-
Notifications
You must be signed in to change notification settings - Fork 957
Fix custody context initialization race condition that caused panic #8391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
mergify
merged 7 commits into
sigp:release-v8.0
from
jimmygchen:fix-custody-context-race
Nov 17, 2025
Merged
Fix custody context initialization race condition that caused panic #8391
mergify
merged 7 commits into
sigp:release-v8.0
from
jimmygchen:fix-custody-context-race
Nov 17, 2025
Conversation
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
8d310a5 to
770e1e5
Compare
60e06f8 to
0e80706
Compare
28c2073 to
935db19
Compare
jimmygchen
commented
Nov 12, 2025
michaelsproul
approved these changes
Nov 16, 2025
Member
michaelsproul
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks a lot nicer without the expects, and the extra plumbing for initialisation doesn't seem too bad. Looks good!
michaelsproul
approved these changes
Nov 17, 2025
6 tasks
mergify bot
pushed a commit
that referenced
this pull request
Nov 20, 2025
This hot fix release includes the following fixes: * #8388 * #8406 * #8391 * #8413 Co-Authored-By: Jimmy Chen <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
ready-for-merge
This PR is ready to merge.
v8.0.1
Cheeky patch release for Fulu
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.
Issue Addressed
Take 2 of #8390.
Fixes the race condition properly instead of propagating the error. I think this is a better alternative, and doesn't seem to look that bad.
Proposed Changes
NetworkServicestartup to theClientBuilder, so that it can be used to compute custody columns for the beacon chain without waiting for Network bootstrap.I've considered and implemented a few alternatives:
node_idto beacon chain builder and compute columns when creatingCustodyContext. This approach isn't good for separation of concerns and isn't great for testabilityordered_custody_groupsto beacon chain.CustodyContextonly uses this to compute ordered custody columns, so we might as well lift this logic out, so we don't have to do error handling inCustodyContextconstruction. Less tests to update;.