-
Notifications
You must be signed in to change notification settings - Fork 0
Merge Geth [v1.15.0...v1.15.11] #499
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
Conversation
|
You can try to accept |
|
The merge of |
This issue has already been created. #507 |
Starting the 7CNs privnet will get stuck at block 30. |
There seems something wrong in synchronization and reorg, just for reference. I can spend some time looking into it. Fixed, but this time a test |
@qianhh I reworked the low level chain implementation based on bsc, there is no Have a try on 4bc167f. I wish we can merge this part from upstream in this PR, because IMO it is an essential part of v1.15, maybe even the beacon consensus changes. |
OK, I'll test it again. The BSC issue was resolved because the consensus was separated from the beacon and no longer used the beacon for packaging. That is, a post-merge process was carried out. I also implemented a version(624241e) based on BSC, the test results seem to be fine. |
This is an attempt to work around a gcc issue in the Docker build.
This reverts commit 7b96ec4dae8d4ddeffc761c7757c12e2d2b8bf74.
This changes the `-upload` flag to just toggle the upload. The remote image name is now configured using the `-hub` flag.
This PR builds on #29040 and updates it to the new version of the spec. I filled the EEST tests and they pass. Link to spec: https://eips.ethereum.org/EIPS/eip-7623 --------- Co-authored-by: Marius van der Wijden <[email protected]> Co-authored-by: lightclient <[email protected]> Co-authored-by: lightclient <[email protected]>
Finalize Prague system contract addresses. Reference: * ethereum/EIPs#9287 * ethereum/EIPs#9288 * ethereum/EIPs#9289
I caught this error on Hive. It was introduced by ethereum/go-ethereum#31071 because after adding the equality check the request type 0 will be rejected.
Removes duplicate code in the interpreter loop.
Fixes a typo in the error message within the `fuzzCrossG2Add` function. The panic message incorrectly references "G1 point addition mismatch" when it should be "G2 point addition mismatch," as the function deals with G2 points. This doesn't affect functionality but could cause confusion during debugging. I've updated the message to reflect the correct curve.
This is a follow-up PR to #29792 to get rid of the data file sync. **This is a non-backward compatible change, which increments the database version from 8 to 9**. We introduce a flushOffset for each freezer table, which tracks the position of the most recently fsync’d item in the index file. When this offset moves forward, it indicates that all index entries below it, along with their corresponding data items, have been properly persisted to disk. The offset can also be moved backward when truncating from either the head or tail of the file. Previously, the data file required an explicit fsync after every mutation, which was highly inefficient. With the introduction of the flush offset, the synchronization strategy becomes more flexible, allowing the freezer to sync every 30 seconds instead. The data items above the flush offset are regarded volatile and callers must ensure they are recoverable after the unclean shutdown, or explicitly sync the freezer before any proceeding operations. --------- Co-authored-by: Felix Lange <[email protected]>
This PR fixes a data race in SetupGenesisWithOverride.
|
@qianhh I think I've fully merged ethereum/go-ethereum#31414, please check and update the PR introduction if possible. This feature needs testing as well. |
*: revert customized behaviors about finalized block
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.
LGTM now, further improvement is still welcome.
|
Seems like I misunderstood the blob data handling, the current EL implementation is only a collector of blob transaction. There are two store-and-prune places for blob data in the Ethereum network:
The whole life cycle of a blob is like the following:
Since the EL temporary storage implemented with https://github.com/holiman/billy, it is not designed to persist a blob for its full life cycle, and we don't have methods to access them correctly. go-ethereum/core/txpool/blobpool/slotter.go Lines 19 to 38 in d32fea9
About the db design, we can refer to its introduction. If we refer to the configuration of billy shelves, it defines a fixed number of shelves for a specific I can't leave this storage keeping increasing, it's not publicly accessible or efficient, because it is only designed to handle PoS reorgs. Let's solve this in #520, here we give it a fallback value for pruning. |
783a0a8 to
a073b73
Compare
|
@songb2 detected a transaction root mismatch error with blob transactions in dBFT, checking. |
Fixed, the root is dBFT fetched full blob data from local pool, but sidecar should not be included in the block. |
|
@songb2 Open issues if you find any error, I'm going to merge. |
This PR merges v1.15.0...v1.15.11 of Geth into bane-main and aimed to close #496 and #517.
Progress
The list of important PRs that were merged. @AnnaShaleva, @txhsl, please have a look at these PRs before the review.
Merged but Reverted
dbft.