feat: orderPriority for deterministic service start order - #11
Merged
Conversation
Sort ready services by (orderPriority, name) via BTreeSet Kahn so lower priority starts earlier while dependsOn remains a hard DAG edge. Co-authored-by: Cursor <cursoragent@cursor.com>
This was referenced Aug 8, 2026
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.
Summary
orderPriority(default 100) to service JSON / RustServiceConfig/ GoServiceDef(orderPriority, name)among ready services viaBTreeSetdependsOnremains a hard DAG edgeTest plan
cargo test --test graph_testgo test ./config/...cargo test --tests(supervisor timing flake may appear unrelated)orderPrioritydeserializes to 100Made with Cursor