-
Notifications
You must be signed in to change notification settings - Fork 213
Merge 1.9.10 upstream #1115
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 1.9.10 upstream #1115
Conversation
* core: fix staticcheck warnings * fix goimports
core/rawdb: fix reinit regression caused by the hash check PR
deps: update fastcache to 1.5.3
The original idea behind this change was to remove a use of the deprecated CancelRequest method. Simply removing it would've been an option, but I couldn't resist and did a bit of a refactoring instead. All remote sealing code was contained in a single giant function. Remote sealing is now extracted into its own object, remoteSealer.
This change: - removes the PostChainEvents method on core.BlockChain. - sorts 'removed log' events by block number. - fire the NewChainHead event if we inject a canonical block into the chain even if the entire insertion is not successful. - guarantees correct event ordering in all cases.
trie: track dirty cache metrics, track clean writes on commit
params: update CHTs for v1.9.9 release
* consensus/ethash, params: implement eip-2384: bump difficulty bomb * params: EIP 2384 compat checks * consensus, params: add Muir Glacier block number (mainnet,ropsten) + official name * core/forkid: forkid tests for muir glacier * params/config: address review concerns * params, core/forkid: review nitpicks * cmd/geth,eth,les: add override option for muir glacier * params: nit fix
1.to build stress tests Depends-On: 6269e55
…910) * fuzzers: fuzzers for keystore, rlp, trie, whisper (cred to @guidovranken) * fuzzers: move fuzzers to testdata * testdata/fuzzers: documentation * testdata/fuzzers: corpus for rlp * tests/fuzzers: fixup
core: removed old invalid comment
appveyor: bump Go to 1.13.6 on Windows
travis: bump Android builder to Go 1.13.6
params: update CHTs for v1.9.10 release
# Conflicts: # accounts/usbwallet/ledger.go # cmd/geth/config.go # cmd/geth/main.go # consensus/ethash/algorithm_test.go # consensus/ethash/api.go # consensus/ethash/consensus.go # consensus/ethash/ethash.go # consensus/ethash/sealer.go # consensus/ethash/sealer_test.go # core/blockchain.go # core/blockchain_test.go # core/forkid/forkid_test.go # core/genesis.go # core/vm/contracts.go # les/client.go # les/txrelay.go # miner/stress_clique.go # miner/stress_ethash.go # miner/worker.go # miner/worker_test.go # params/config.go # params/version.go
# Conflicts: # Makefile # README.md # accounts/abi/bind/backends/simulated.go # accounts/abi/bind/backends/simulated_test.go # build/checksums.txt # build/ci.go # cmd/puppeth/module_dashboard.go # consensus/ethash/consensus.go # core/blockchain.go # core/headerchain.go # core/tx_list.go # core/tx_pool.go # light/lightchain.go # params/config.go # params/version.go
This upstream PR ethereum/go-ethereum#20453 (which is actually a fix for a bug that @asaj submitted to upstream geth) should make this celo-blockchain PR unnecessary and revert-able: #333. One thing to consider if the celo-blockchain PR is reverted is if it will still be backwards compatible. |
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! Regarding this comment (#1115 (comment)), I suppose it's not totally necessary to revert the PR for this merge.
However, if you decide not to revert the PR, then please create an issue for it.
Description
Tested
Backwards compatibility
Yes