Update/upstream #10
Merged
Update/upstream #10
Conversation
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 error will never happen, but if it ever does happen, we will at least see it.
* trie, core/state: revert error removal in (*state.Trie).Commit * Gary's nitpick :) Co-Authored-By: rjl493456442 <[email protected]> --------- Co-authored-by: rjl493456442 <[email protected]>
* eth: send big transactions by announce/retrieve only * Update eth/handler.go Co-authored-by: Martin Holst Swende <[email protected]> * eth: remove superfluous bracket * eth: add whitespace --------- Co-authored-by: Martin Holst Swende <[email protected]>
* params, trie: add verkle fork management + upgrade go-verkle * remove the two verkle files * core, eth, params: add missing function * Gary's feedback * remove trie/utils/verkle.go * add verkle block override --------- Co-authored-by: Gary Rong <[email protected]>
…nt (#27209) * core/state, light, les: make signature of ContractCode hash-independent * push current state for feedback * les: fix unit test * core, les, light: fix les unittests * core/state, trie, les, light: fix state iterator * core, les: address comments * les: fix lint --------- Co-authored-by: Gary Rong <[email protected]>
…7525) The clean trie cache is persisted periodically, therefore Geth can quickly warmup the cache in next restart. However it will reduce the robustness of system. The assumption is held in Geth that if the parent trie node is present, then the entire sub-trie associated with the parent are all prensent. Imagine the scenario that Geth rewinds itself to a past block and restart, but Geth finds the root node of "future state" in clean cache then regard this state is present in disk, while is not in fact. Another example is offline pruning tool. Whenever an offline pruning is performed, the clean cache file has to be removed to aviod hitting the root node of "deleted states" in clean cache. All in all, compare with the minor performance gain, system robustness is something we care more.
This removes text parsing in leveldb metrics collection code. All metrics can now be accessed through the stats API provided by leveldb. We also add new gauge-typed metrics that count the number of tables at each level. --------- Co-authored-by: Exca-DK <[email protected]> Co-authored-by: Gary Rong <[email protected]> Co-authored-by: Felix Lange <[email protected]>
core (blockchain_test): add chain.Stop() to tests
Co-authored-by: Martin Holst Swende <[email protected]>
This change adds back the 'geth --dev' mode of operation, using a cl-mocker. --------- Co-authored-by: Martin Holst Swende <[email protected]> Co-authored-by: rjl493456442 <[email protected]> Co-authored-by: lightclient <[email protected]>
This PR adds metrics for p2p dialing, which gives us visibility into the quality of the dial candidates returned by our discovery methods.
Back before #27178 , we spun up a number of ethash verifiers to verify headers. So we also had tests to ensure that we were indeed able to abort verification even if we had multiple workers running. With PR #27178, we removed the parallelism in verification, and these tests are now failing, since we now just sequentially fire away the results as fast as possible on one routine. This change removes the (sometimes failing) tests
Implements [EIP 5656](https://eips.ethereum.org/EIPS/eip-5656), MCOPY instruction, and enables it for Cancun. --------- Co-authored-by: Martin Holst Swende <[email protected]>
Fixes an issue where waitgroups were used erroneously, which could lead to waitgroup being added to while wait was already invoked.
This change makes the StateDB track the state key value diff of a block transition. We already tracked current account and storage values for the purpose of updating the state snapshot. With this PR, we now also track the original (pre-transition) values of accounts and storage slots.
This simplifies the code that initializes the discovery a bit, and adds new flags for enabling/disabling discv4 and discv5 separately. --------- Co-authored-by: Felix Lange <[email protected]>
This change adds the ability to perform reads from freezer without size limitation. This can be useful in cases where callers are certain that out-of-memory will not happen (e.g. reading only a few elements). The previous API was designed to behave both optimally and secure while servicing a request from a peer, whereas this change should _not_ be used when an untrusted peer can influence the query size.
This prevents an issue where the node would attempt to contact the bootstrap nodes even if they weren't contained in the netrestrict list.
fix function name in comment Signed-off-by: cui fliter <[email protected]>
* eth: rm redundant type from array, slice, or map * miner: rm redundant type from array, slice, or map
graphql: fix race in test
internal/ethapi: fast exit if tx notfound
…#133) This removes the overrides for Optimism, Bedrock, and Regolith. All of these forks have already been activated. This creates an override for the next network upgrade called Canyon.
…_12_2 Update to Geth v1.12.2 Mawinor
…ta-mcp flags: remove beta prefix from rollup.halt flag
When changing fork.yaml, it is useful to check the updated output without relying on CI.
…-make-target Add make target to create local forkdiff output
…_13_1 Update to Geth v1.13.1 (Zakros) - [depends on ethereum-optimism#136 v1.12.2 update]
…posittx-receipt-encoding
…t-protocol-versions go.mod: update superchain-registry for devnet network option
Signed-off-by: protolambda <[email protected]>
params: add chaosnet, update superchain-registry
…t-config-fix params: devnet config fix
…-config-db superchain: beta feature flag for overriding chain-config with superchain-registry
|
|
sveitser
approved these changes
Oct 31, 2023
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.
No description provided.