Repository navigation
A command may be accepted before there is capacity for it: the wait is told as an event, bounded, and ends in an outcome - #114
Closed
riccardone wants to merge 1 commit into
Closed
riccardone wants to merge 1 commit into
riccardone wants to merge 1 commit into
Conversation
…s told as an event, bounded, and ends in an outcome Entries 42, 42a and 49 of #37, one need: a command that waits its turn. The spec defines no timeout protocol and says nothing of a command accepted now and run later, of bounds on that wait and on the run, or of ending such a command before it began. best-peer queues an order that asks to wait, tells JobQueued, bounds the wait and the run from its own events' times, tells the bound it applies when the caller named none, and stops a waiting order with the same stop-job. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Contributor
Author
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.
Entry 42, 42a and 49 (one need: a command that waits its turn) on #37 (#37), proven by best-peer.
Why
Command Results says "BEST defines no timeout protocol" and callers decide how long to wait. It says nothing of a command accepted now and run later because the service has no capacity yet, of bounds the caller sets on that wait and on the run, of ending such a command before it began, or of what bounds a wait the caller did not bound. best-peer, at a machine's door and at the cloud above it alike: an order that asks to wait is taken (
201) and told asJobQueued, placed first come first served;queue_secondsbounds the wait (past it,JobFailedsays it was never placed) anddeadline_secondsthe run (past it,JobStoppedsays why), both counted from the events' own times so a restart neither resets nor extends them; an order that names noqueue_secondswaits a day at most, and that bound is written onJobQueued;stop-jobends a waiting order before it started. At a machine, an order that does not ask to wait is refused at once when there is no room, so a cloud distributing work is not held by one full machine.What
A subsection of Command Results and Correlation, Commands That Wait, placed after the paragraph #100 changes so the two do not touch.
Nothing changes in the conformance list: the sentence is a clarification.
No version bump and no release notes here: the PRs from #37 do not collide that way, and the release that gathers them does both.
🤖 Generated with Claude Code