* moved TxDependency Metadata to ExtraData in Block Header
* updated unit tests
* lints
* small bug fix
* small improvement
* minor bug fix
* addressed comments
* bug fix, only using the BlockExtraData structure after the Parallel Universe HF
* addressed comments
* fixed an error
* bug fix
* encoding nil ValidatorBytes and TxDependency in prepare if the current block is not the last block of the sprint
* bug fix
* rpc: add execution pool metrics
* rpc: stop execution pool and report metrics using ticker
* fix lint
* update go.mod, update metric report interval
* handle empty workerpool case to fix tests
* fix lint
* refactor ep metrics collection based on each service
* remove log
* rpc: convert processed metric to histogram
* dev: chg: pos-1605: fix govulns by bumping golang version and replacing mongodb version
* dev: chg: pos-1605: update some dependencies to solve dependabot vulns
* dev: chg: update linter for compatibility with upgraded go version
* dev: chg: update go version in golangci lintere
* dev: chg: update go version in ci workflow, docker and travis
* dev: chg: change govulncheck version to a stable fixed one
* dev: chg: fix govulncheck version
* dev: chg: remove vulncheck version
* dev: chg: adapt tests based on go-ethereum for go version upgrade
* dev: chg: use explicit go version for templum action
* dev: chg: fix lint
* dev: chg: fix lint
* dev: chg: 1.20.x explicitly in packager
* dev: chg: ignore some additional leak to be fixed
* dev: chg: ignore some additional leak to be fixed
* dev: chg: fix lint
The `baseFee` can be `nil` in certain situations, the tracing must not use `baseFee` unless it was checked otherwise if such case happen, Go is going to panic.
Currently, we determine if MVHashMap should be enabled by checking the block number with parallelUniverse flag in genesis, which has a value of 0. Some headers' block number is 0, so MVHashMap was enabled, which led to a few errors. Disable this flag explicitly until we figure out a proper hardfork solution.
A reverted transaction, X, can incorrectly write to a slot, which might be read by another transaction, Y. If we skip checking states written by X, then Y might end up with reading the wrong value and we won't be able to detect this error.
* updated Indore HF related changes by adding stateSyncConfirmationDelay
* converted StateSyncConfirmationDelay to map[string]uint64 and cleanup
* calculate last state ID from incoming state object with eth call (#883)
* removed IndoreBlock from configs
* fix
* remove code duplication and refactor
---------
Co-authored-by: Manav Darji <manavdarji.india@gmail.com>
An address's nonce and balance will get updated even if its transaction is reverted. Therefore, we need to keep balance and nonce in write list in order to check the transaction's validity in parallel execution.
