Harden worker dispatch and installation checks - #16
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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.
An external claims collector could hide this router's existing launches, and alternate filesystem spellings or nested workspaces could admit overlapping workers. Dispatch now checks fresh durable receipts under its lock and compares canonical paths and filesystem ancestry. Bounded receipt scans, recorded phases, persistent launch intents and
route-statusmake failures diagnosable while preserving reservations after uncertain native outcomes.Installation now rejects occupied selected ports before provisioning, including qdrant's gRPC port, and rechecks immediately before startup.
borg startdistinguishes process liveness from verified readiness. The installer entry point and test fixtures are covered, adapter compatibility wording is clarified, and Linux/macOS CI verifies the exact public inventory plus the conductor with a real isolated Codex app-server.Validation:
Existing installed homes are not migrated. New-owner provider login, full Linux/Intel installation and external Cloudflare setup remain separate acceptance steps. Legacy intents retain their original path spelling for lookup; unknown starts are not automatically retried.