Repository navigation
Write capability trees with bounded concurrency - #619
Merged
SaladDay merged 1 commit intoOct 9, 2026
Merged
Conversation
SaladDay
marked this pull request as ready for review
October 9, 2026 12:56
SaladDay
deleted the
aos/write-capability-trees-with-bounded-concurrency
branch
October 9, 2026 12:57
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.
Environment finalization wrote and synced capability trees serially across the File boundary. Bound file writes and the following directory-sync phase to the declared handle limit (at most four), retaining serial ownership, complete task settlement, independent handle cleanup, and all manifest readback and integrity checks. Any uncertain mutation still quarantines the owner; failed file or directory phases cannot publish a manifest.
The existing composition fixture keeps all 393 RPCs and measures about 19% lower finalization latency at injected 20 ms and 100 ms per-call delays (5.956→4.792 s and 29.254→23.627 s). Zero-delay results show no claimed speedup and a small allocation increase. This is local measurement; the real micro lifecycle remains unqualified.
Validation: focused real File-service tests cover declared limits 1–4, mixed effect certainty, cancellation and late replies, cleanup failures, publication ordering, partial writes, and serial replacement. Concurrency tests pass race ×50; postcommit agenthost/capabilities tests pass 102 cases with six existing prerequisite skips. Focused vet and check-names/check-docs/check-ci pass. Root full-diff review and fresh independent review found no in-scope issues; the reviewer also passed focused race tests. CI is running.