Repository navigation
Observe runtime readiness and wake capability-driven scheduling - #10
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Cold Runtime admission currently waits for periodic candidate scans after capabilities become available, and its logs do not distinguish actual transport registration from lifecycle observation. This change records authenticated registration and confirmed current capability snapshots, adds daemon discovery/bootstrap/dial timings, and sends coalesced capability hints through the existing scheduler gates.
The hints retain lease, capacity, current credentials, lifecycle phase, capability and cancellation validation, with polling as recovery. Malformed, replaced, disconnected, revoked and retired peers cannot produce accepted observations or hints; temporary confirmation failure retains the pending observation. No SQL, migration, wire protocol or native package pin changes. Daemon timings require a rebuilt Runtime template.
Validation: focused gateway/execution/CLI regressions and race checks; isolated PostgreSQL scheduling, Worker admission and device-isolation fixtures; Runtime contract, go vet, name/documentation and full translation checks. Fresh independent review completed without blocking findings.