forked from ethereum/go-ethereum
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Merge/v1.13.15 #175
Merged
Merged
Merge/v1.13.15 #175
Commits on Apr 17, 2024
-
eth/protocols/snap: skip retrieval for completed storages (ethereum#2…
…9378) * eth/protocols/snap: skip retrieval for completed storages * eth/protocols/snap: address comments from peter * eth/protocols/snap: add comments
Configuration menu - View commit details
-
Copy full SHA for 5dcf503 - Browse repository at this point
Copy the full SHA 5dcf503View commit details -
Configuration menu - View commit details
-
Copy full SHA for e343ddf - Browse repository at this point
Copy the full SHA e343ddfView commit details -
eth/filters: enforce topic-limit early on filter criterias (ethereum#…
…29535) This PR adds a limit of 1000 to the "inner" topics in a filter-criteria
Configuration menu - View commit details
-
Copy full SHA for 7bcb553 - Browse repository at this point
Copy the full SHA 7bcb553View commit details -
core, eth/protocols/snap, trie: fix cause for snap-sync corruption, i…
…mplement gentrie (ethereum#29313) This pull request defines a gentrie for snap sync purpose. The stackTrie is used to generate the merkle tree nodes upon receiving a state batch. Several additional options have been added into stackTrie to handle incomplete states (either missing states before or after). In this pull request, these options have been relocated from stackTrie to genTrie, which serves as a wrapper for stackTrie specifically for snap sync purposes. Further, the logic for managing incomplete state has been enhanced in this change. Originally, there are two cases handled: - boundary node filtering - internal (covered by extension node) node clearing This changes adds one more: - Clearing leftover nodes on the boundaries. This feature is necessary if there are leftover trie nodes in database, otherwise node inconsistency may break the state healing.
Configuration menu - View commit details
-
Copy full SHA for 35e0525 - Browse repository at this point
Copy the full SHA 35e0525View commit details -
Configuration menu - View commit details
-
Copy full SHA for c5ba367 - Browse repository at this point
Copy the full SHA c5ba367View commit details
Commits on May 6, 2024
-
Merge tag 'v1.13.15' into merge/v1.13.15
Austin Roberts committedMay 6, 2024 Configuration menu - View commit details
-
Copy full SHA for ed1f7ae - Browse repository at this point
Copy the full SHA ed1f7aeView commit details -
Configuration menu - View commit details
-
Copy full SHA for 75b5452 - Browse repository at this point
Copy the full SHA 75b5452View commit details
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.