about summary refs log tree commit diff
path: root/test/python/auth_helpers.py
diff options
context:
space:
mode:
authorPjotr <wrk@bosa.lan>2026-10-12 15:57:46 +0000
committerPjotr <wrk@bosa.lan>2026-10-12 15:57:46 +0000
commit9cc1631324216d564aca4448cbe71f49dbf2a4af (patch)
treec975e39607738065f108dc0577c6fbac7e501a1b /test/python/auth_helpers.py
parentb04db9ea05a73074afcf88300f8b6aa8c6e28e64 (diff)
downloadgenenetwork4-9cc1631324216d564aca4448cbe71f49dbf2a4af.tar.gz
gemma: rename peak to peek; reject a reused run id with 409
peak -> peek: the status endpoint's byte-offset query parameter and
everywhere it's documented (code comments, the GemmaStatusParams
field, tests, README). GeneNetwork3's own equivalent
(gn3/api/streaming.py) is spelled "peak"; noted where this now
deliberately differs, not touching the unrelated "peak marker" wording
elsewhere in the README.

Run id uniqueness: the log file is now created with
OpenOptions::create_new(true) instead of a plain truncating write, so
it fails atomically (no separate check-then-write race) if a log
already exists for that id -- another run still in progress, or a
finished one never polled/cleaned up. Added GemmaError::RunIdInUse,
mapped to 409 Conflict in the route, caught before any subprocess
runs. Previously a reused id would have silently truncated whatever
was already there.

Verified: the new compute_gemma_rejects_a_run_id_already_in_use test
pre-seeds a log file for an id and confirms the POST is refused (this
needs no gemma-wrapper, since the check runs before any subprocess
call). cargo test passes in full.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Diffstat (limited to 'test/python/auth_helpers.py')
0 files changed, 0 insertions, 0 deletions