You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(mothership): explain a Chat turn the worker ends without a reason (#8478)
* fix(mothership): explain a Chat turn the worker ends without a reason
When the worker rebuilds an ended run from its log (a resume or reattach
that reaches a run that already ended, for example at its deadline), it
sends an error terminal with no error event. Sim then fell back to the
generic "An unexpected error occurred while processing the response."
The turn now says the run had already ended and can be continued by
sending a message. A reason the worker reports, a replay refusal, and a
Stop all still take precedence.
Also:
- Log the Go stream's error text under errorMessage/detail so it no longer
overwrites the log line's own message (stream.ts, buffer.ts).
- Rename STREAM_TIMEOUT_MS to CHAT_RUN_DEADLINE_MS and document it as the
worker's default run deadline, now only the base of USAGE_SETTLE_MS.
- Update the byte-budget doc: a reader behind the ring trim is re-synced
from the worker log; replay_gap is only the fallback.
* fix(mothership): keep the ended-run message surface-neutral and below a replay refusal
The fallback is shared by Chat, workflow execute and inbox, so it no longer
tells the reader to send a message. A replay refusal now wins by guard rather
than by spread order, with a test that covers the combination.
* refactor(mothership): drop the unreachable refusal guard and reuse the stream-abort test helper
0 commit comments