Repository navigation
Add allowance CLI and owner admission fields - #407
Merged
Merged
Conversation
added 5 commits
October 7, 2026 13:57
Identify the additive owner admission and unknown drain fields with a new API minor version so clients can detect their availability. GitHub issue #215.
This was referenced Oct 7, 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.
dbl allowancereports the authenticated account’s granted, reserved, consumed and remaining non-monetary TEST units without losing integer precision. API 1.20 adds owner-scoped admission status and explicitly unavailable host drain observations, preserving existing connection-status semantics.The API guide specifies nonbinding quote snapshots and review of repriced intents before payment or submission. The external pilot procedure now requires a signed release, records proxy/TLS paths, and distinguishes a fresh stopped-state restore from restart or unsupported historical rollback.
Concurrent runtime shutdown also preserves an already established caller cancellation cause when Close runs before that cancellation reaches the guest context. A deterministic regression reproduces that ordering.
Validation: focused CLI, HTTP API and SDK race checks passed on Linux, followed by API version/contract/owner checks. The cancellation regression and lifecycle ownership checks passed 30 race iterations, and real guest CPU/read/output cancellation and direct-close checks passed five race iterations. Documentation links and whitespace checks passed. Console adoption and external pilot acceptance remain separate requirements.
Related: #83, #214, #215, #21.