Skip to content

Merge main into next: hold requests while an engine drains (#340) - #341

Merged
T-Crypt merged 4 commits into
nextfrom
T-Crypt/main-into-next-hold-draining
Nov 15, 2026
Merged

T-Crypt merged 4 commits into
nextfrom
T-Crypt/main-into-next-hold-draining

Conversation

@T-Crypt

@T-Crypt T-Crypt commented Nov 15, 2026

Copy link
Copy Markdown
Owner

Brings #340 from main into next. The tree matches main, and the CHANGELOG lines sit under Unreleased. The full proof passed on this tree.

A draining engine still answers its probe, so the gateway proxied the next
request to it. On aphotic at 12:45:22 on 2026-11-15, the runner read Strata
idle, began to unload it, and Strata took the next agent turn in the two
seconds it spent stopping and ended it with 0 tokens (finish=length).

resolve no longer treats an engine as live while its lease is draining,
parking or releasing, and ensure waits for that lease to settle before it
probes. Active again, the request goes on to the engine. Gone, the engine
stops answering and the gateway starts it anew, waiting for the card as any
start does.
…ning

fix(gateway): hold a request while its engine's lease drains
@T-Crypt
T-Crypt merged commit b6ce5fb into next Nov 15, 2026
2 checks passed
@T-Crypt
T-Crypt deleted the T-Crypt/main-into-next-hold-draining branch November 15, 2026 21:26
@T-Crypt T-Crypt mentioned this pull request Nov 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant