Repository navigation
Avoid an empty environment input scan interval - #31
Merged
Merged
Conversation
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
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.
A pending input whose Runtime reconnects before it becomes ready can be skipped by the scheduler, then wait an extra five-second scan just to reset the exhausted cursor. Refill the first page once at EOF so that input can be retried on the next scheduled scan.
The five-second cadence, 100-candidate bound, four active slots, Session ownership, queue alternation and reservation deadlines remain intact. No provider, harness, API or database changes.
Validation:
make checkpassed, including all 74 Web acceptance cases. Readiness retry, 101-candidate pagination, mixed-queue capacity and retry/deadline regressions pass; the new readiness regression reproduces the extra interval on the unchanged baseline (10.77 seconds).Turn.started_at, not first token or model completion.All four runs verified same-Session history/files/configuration, one-time initialization, idempotent retry, source VM resource release, and restoration of the exact snapshot. The two sub-10-second resume observations are not a percentile/SLA or an uncached-image benchmark; cold start remains above 10 seconds.
GitHub
sessionsrun passed dedicated execution persistence, then reproduced the pre-existing CI-001 assertion atofficial_agent_references.py:73(Expected BadRequestErrorfor supported multi-agent enablement); its downstream container stage was skipped. No unrelated test or behavior was changed. GitHubcheckpassed, including the standalone gate and execution-daemon build. All task-owned test compute, snapshots, databases, proxies, tunnels and copied credentials have been cleaned up.Document A records the decision, validation and remaining limits.