Fix bold StopWaiter lifecycle: start children on their own StopWaiters#4487
Merged
rauljordan merged 7 commits intomasterfrom Mar 13, 2026
Merged
Fix bold StopWaiter lifecycle: start children on their own StopWaiters#4487rauljordan merged 7 commits intomasterfrom
StopWaiter lifecycle: start children on their own StopWaiters#4487rauljordan merged 7 commits intomasterfrom
Conversation
The assertion manager has its own StopWaiter but was being started via the parent challenge manager's LaunchThread, creating two overlapping lifecycle mechanisms for the same component.
Similar pattern as for the assertion manager.
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #4487 +/- ##
==========================================
+ Coverage 34.56% 34.59% +0.02%
==========================================
Files 495 495
Lines 58648 58649 +1
==========================================
+ Hits 20272 20289 +17
+ Misses 34772 34760 -12
+ Partials 3604 3600 -4 |
Contributor
❌ 10 Tests Failed:
View the top 3 failed tests by shortest run time
📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
rauljordan
approved these changes
Mar 11, 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
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
StopWaiterlifecycle: The assertion manager, chain watcher, and API server each have their ownStopWaiterbut were started via the parent challenge manager'sLaunchThread, creating two overlapping lifecycle mechanisms per component. Now each child starts on its ownStopWaiterwith a non-blockingStart()method, so goroutines are tracked by the struct that owns them.StopAndWaitordering: The challenge manager was stopping itself before its children, cancelling the parent context before children could shut down gracefully. Children are now stopped first.BOLDStakerwas passing the raw input context to the challenge manager instead of its managed context, soStopWaitercancellation wouldn't propagate through the hierarchy.These are the only misuses I could find either manually or with Claude in
bold/andstaker/bold/directories.closes NIT-2974