core/state: copy trie too, not just content#15549
Merged
Merged
Conversation
Contributor
|
I'm thinking maybe it would be worth to have a testcase about this? To ensure that future changes does not break this, and that the copy mechanism is sufficiently deep. |
Member
Author
|
@holiman I've added a test that panics without the copy fix. PTAL. |
Arachnid
approved these changes
Nov 24, 2017
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.
When copying the statedb (used by the RPC to access the pending state), we have not copied the trie, only the state objects. This means that if the RPC would have modified the state, it would have corrupted the miner. This does not happen currently (AFAIK).
We need this fix in for concurrent block tracing with shared statedbs.