This makes non-JS tracers execute all block txs on a single goroutine.
In the previous implementation, we used to prepare every tx pre-state
on one goroutine, and then run the transactions again with tracing enabled.
Native tracers are usually faster, so it is faster overall to use their output as
the pre-state for tracing the next transaction.
Co-authored-by: Sina Mahmoodi <itz.s1na@gmail.com>
This PR removes the notion of fakeStorage from the state objects, and instead, for any state modifications that are needed, it simply makes the changes.
* p2p/discover: add more packet information in logs
This adds more fields to discv5 packet logs. These can be useful when
debugging multi-packet interactions.
The FINDNODE message also gets an additional field, OpID for debugging
purposes. This field is not encoded onto the wire.
I'm also removing topic system related message types in this change.
These will come back in the future, where support for them will be
guarded by a config flag.
* p2p/discover/v5wire: rename 'Total' to 'RespCount'
The new name captures the meaning of this field better.
Alarm is a timer utility that simplifies code where a timer needs to be rescheduled over
and over. Doing this can be tricky with time.Timer or time.AfterFunc because the channel
requires draining in some cases.
Alarm is optimized for use cases where items are tracked in a heap according to their expiry
time, and a goroutine with a for/select loop wants to be woken up whenever the next item expires.
In this application, the timer needs to be rescheduled when an item is added or removed
from the heap. Using a timer naively, these updates will always require synchronization
with the global runtime timer datastructure to update the timer using Reset. Alarm avoids
this by tracking the next expiry time and only modifies the timer if it would need to fire earlier
than already scheduled.
As an example use, I have converted p2p.dialScheduler to use Alarm instead of AfterFunc.
This changes moves the tracking of "deleted in this block" out from snap-only domain, so that it happens regardless of whether the execution is snapshot-backed or trie-backed.
* added support for dependencies (executor_tests)
* added a function to get dependency map
* getting all dependencies in the GetDep function
* updated GetDep function
* changed the type of AllDeps
* added a function to get dependency map
* updated GetDep function
* generate and get dependencies from block producer
* optimized getDep function
* bug fix regarding txn index and dep structure
* fixed gas bug
* optimized getDep function
* tests updated/added
* few updates regarding dependencies
* added channel to calculate the dependencies in a separate go routine
* minor changes in the executor which uses latest changes of dependecies + removed metadata flag/argument
* Use channel when metadata is available
* small bug fix
* getting reads and writes only when the transaction succeeds
* fixed bug in adding dependencies
* updated logic for delay/not delay
* bug fix (shouldDelayFeeCal) in parallel state processor
* lint fix
* using EnableMVHashMap flag
* fixed worker and stateProcessor and removed SetMVHashMapNil fumction from stateDB
* addredded few comments and fixed bug in executor tests
* commented executor tests with metadata (panic: test timed out after 5m0s)
* added a check to check len(mvReadMapList) > 0 in miner
* addressed comments, minor refactoring in dag.go
* moved blockContext out of Execute and adding it in execution task
* removed Author() from Settle() and added in execution task
* not calling block.Header() again and again, using instead
* removed EnableMVHashMap flag, and updated applyTransaction function
* addressed comments
* added unit test to check dependencies in the block header
Co-authored-by: Jerry <jerrycgh@gmail.com>
This changes the StorageTrie method to return an error when the trie
is not available. It used to return an 'empty trie' in this case, but that's
not possible anymore under PBSS.
This PR builds on #26299, but also updates the tests to the most recent version, which includes tests regarding TheMerge.
This change adds checks to the beacon consensus engine, making it more strict in validating the pre- and post-headers, and not relying on the caller to have already correctly sanitized the headers/blocks.
This PR implements resettable freezer by adding a ResettableFreezer wrapper.
The resettable freezer wraps the original freezer in a way that makes it possible to ensure atomic resets. Implementation wise, it relies on the os.Rename and os.RemoveAll to atomically delete the original freezer data and re-create a new one from scratch.
This PR fixes an error in trie commit. If the trie.root is nil, it can be two possible scenarios:
- The trie was empty, and no change happens
- The trie was non-empty and all nodes are dropped
For the latter one, we should collect the deletions and apply them into database(e.g. in PBSS).
