wai-quantum-service: a job sent again under its key is the same job #607

Merged

dcharlot merged 1 commit from wai/quantum-service-idempotency-2 into main 2026-11-04 10:17:26 -05:00

Conversation 0 Commits 1 Files changed 13 +616 -49

2026-11-03

Transaction Science

wai-quantum-service: a job sent again under its key is the same job ...

A client that lost an answer could not ask again safely: a second
submission was a second job, counted against its limits. And the three MCP
tools that run declared idempotentHint: true, which was not so.

POST /v1/jobs and POST /v1/run take an Idempotency-Key, and the three tools
an idempotency_key. Sent again with the same key and request, a job is
answered with the key's job, before any limit, counting as no submission;
with another request the key is refused (J034), naming no job. A key names
its job while the job is kept, but for a job the service interrupted, which
the key runs again. Records keep the key's digest with the client's name;
one lock makes concurrent sends of one key one job. The tools' hint is now
false: a call without a key is a new job. Calls without a key are not
matched by their request, since a client is an address and that would give
one person's job id to anyone at the address sending the same program.

The command line and the Python client send each job under a fresh key, and
send it again under it where no answer came back, only to a service that
says it keeps keys. The Python client's wait also ends on an interrupted
job, where it ran to its deadline before.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

fd3b7c60d4

• View at this point in history

2026-11-03 17:46:09 -05:00