mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-09-25 01:27:16 +00:00
b9f8c7d7fe
The round-6 scoping fix only cleared the pre-drain snapshot when the drain came back EMPTY. On a nonempty drain the `finally` cleared just the drained ids, so a stale arm — typically a cancel whose cross-replica clear was lost — survived the boundary. It would then immediately seal the continuation meant to answer the steer that had just been injected, and land on an empty boundary as `preempt_incomplete`: the interrupt appears to work, and the answer to it is truncated. A boundary that runs has spent its seal, so everything armed at snapshot time is spent whether or not it came back from the drain. The `finally` now clears the union of the snapshot and the drained ids. Arms that land AFTER the snapshot are still spared — their queue items are live and uninjected, which is the property round 6 added. Also fixes an api-workspace CI failure of mine: `resume.spec.js` stubs `GenerationJobManager` wholesale, and the round-3/4 resume work added two calls (`updateMetadata`, `rearmQueuedPreempts`) the stub did not define, so 34 specs threw. Stub extended. Tests: +2 (a nonempty drain clears a stale snapshot arm; a nonempty drain spares an arm that landed mid-drain). Counterfactually verified — the stale-arm spec fails against the unfixed drain. 132 packages/api specs, 60 resume specs green. |
||
|---|---|---|
| .. | ||
| askUserQuestion.e2e.spec.js | ||
| callbacks.spec.js | ||
| client.contextMetadata.spec.js | ||
| client.memory.spec.js | ||
| client.steerWiring.spec.js | ||
| hitlCheckpoint.e2e.spec.js | ||
| jobReplacement.spec.js | ||
| modelEndHandler.spec.js | ||
| openai.spec.js | ||
| request.resumeMetadata.spec.js | ||
| responses.unit.spec.js | ||
| resume.spec.js | ||
| steer.spec.js | ||
| usageEvents.integration.spec.js | ||
| usageEvents.live.spec.js | ||
| v1.duplicate-actions.spec.js | ||
| v1.spec.js | ||