Repository navigation
feat(concurrent)!: send runner limits through a latest-value mailbox - #140
Merged
greenhat616 merged 1 commit intoOct 21, 2026
Merged
Conversation
The runner manager sent each limit through a bounded channel of 8 that a connecting runner does not read, so repeated splits could fill it. A manager only ever lowers a runner's limit, so it now sends limits through a lock-free single-slot mailbox: a newer limit replaces an unread one and the runner reads only the latest. A runner built with the public `TaskRunnerBuilder::control_signal` still applies every signal in order. BREAKING CHANGE: `TaskRunnerBuilder` fields are private; use its setters. `bolt_load::task::instance` no longer exports `RunnerManager`, `RunnerRegistration`, `ControlSender` and `ControlReceiver`, which only the concurrent task used.
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.
Part 9/13 of the event-loop optimization stack · Breaking API. Stacked on part 8.
Manager limits go through a lock-free single-slot mailbox (
LimitSender/LimitReceiver) instead of a bounded channel, so any number of limits can reach a connecting runner (the root cause behind part 4).BREAKING:
TaskRunnerBuilderfields are private;RunnerManager,RunnerRegistration,ControlSenderandControlReceiverare no longer exported.