Repository navigation
Count authorized requests as activity for the daemon's idle exit - #100
Merged
Merged
Conversation
Attachments alone decided when the shared daemon leaves, so the Rust apps (Shape, Canvas, Query, Recall), which call the API through redrob-engine-client without attaching, saw the daemon they started exit ten minutes later -- possibly under a request still being answered. Both authorization middlewares now mark an authorized request as activity: not idle while one is in flight, and the idle clock restarts when it ends. Status polls (/api/health, /api/clients) do not count, since the launcher's engine card asks every few seconds. Live-checked with the dev entrypoint at --idle-exit 1: a /provider call at 45 s kept the daemon up at 75 s; gone at 120 s. Daemon tests cover the accounting and the status-path rule.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Count authorized requests as activity for the daemon's idle exit
Attachments alone decided when the shared daemon leaves, so the Rust apps (Shape, Canvas, Query, Recall), which call the API through redrob-engine-client without attaching, saw the daemon they started exit ten minutes later -- possibly under a request still being answered. Both authorization middlewares now mark an authorized request as activity: not idle while one is in flight, and the idle clock restarts when it ends. Status polls (/api/health, /api/clients) do not count, since the launcher's engine card asks every few seconds.
Live-checked with the dev entrypoint at --idle-exit 1: a /provider call at 45 s kept the daemon up at 75 s; gone at 120 s. Daemon tests cover the accounting and the status-path rule.