Conversation
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Co-authored-by: lambdaclass-user <github@lambdaclass.com>
Collaborator
Author
|
Found some problematic block ranges again, so changing it to draft |
Member
|
@joshieDo where'd you land here? |
28f7014 to
e4c0a0e
Compare
Collaborator
Author
ci clippy failure unrelated tried some other block ranges, and seems finally fine. |
onbjerg
approved these changes
Feb 27, 2023
Collaborator
onbjerg
left a comment
There was a problem hiding this comment.
Smol nits, otherwise LGTM
onbjerg
approved these changes
Feb 28, 2023
Collaborator
onbjerg
left a comment
There was a problem hiding this comment.
LGTM, not sure if CI related or fixed?
Member
Member
|
Sick - ty |
rakita
reviewed
Mar 1, 2023
| if let Some(value) = val { | ||
| hashed_storage.upsert(address, StorageEntry { key, value })?; | ||
| } | ||
| hashed_storage.upsert(hashed_address, StorageEntry { key, value: val })?; |
Collaborator
There was a problem hiding this comment.
Hey @joshieDo is this statement correct: if the storage key is not found (Is zero) it shouldn't be found in hashed table?
I did some refactoring and this came up. .filter(|v| v.key == key) was a bug but this shouldn't be ( I added unwrap_or_default that is why it compares to U256::ZERO)
want to double check
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.
Continues the work from #1324
Fixes some issues on how the
trieis inserting values into the DB during its execution, and how some of thetestdatais being wrongly generated.Mainly coming from the use of
tx.put::<Table>(k,v)withDUPSORTtables (such asStoragesTrie,PlainStorageState, etc...) where thevalueofsubkeyis not actually overwritten but only appended. One needs to first delete the previous entry, before upserting.Adds
reth dump-stage merkleas well.Future improvements: