-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
core, eth/catalyst: fix race conditions in tests #26790
Merged
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
1a571b5
core, eth, graphql: fix race condition
MariusVanDerWijden e60f668
hacky fix for blockhash data race in graphql
s1na 4e7c39b
graphql: set hash in tx.resolve
s1na a70db38
graphql: get rid of unnecessary fix
MariusVanDerWijden 0a364c1
graphql: avoid writing to block
s1na f138d2e
graphql: split graphql fixes out
MariusVanDerWijden 7d805c2
eth/catalyst: reduce diff
MariusVanDerWijden File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
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.
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.
So, previously, the copied header shares them same withdrawalsHash pointer with the original one?
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.
Yes, it did not surface as a problem, since its only ever read in rlpHash, but still kinda unsafe I think
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.
Sure, we should fix it
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.
First this looked wrong to me, so had to dig a bit.
After the
cpy=*h
, thecpy
and theh
have a pointer to the same hash.The
cpy
have one pointer, theh
have another pointer, and both pointers have the same value. At this point, we know it's not thenil
-value.Previously, we deferred the
cpy
pointer-value, and overwrote it with the contents of theh
pointer value. Which seems to have been a complete no-op, as far as I can tell.So yeah, I totally agree.