Release 1.0 #14
Merged
Release 1.0 #14
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
crypto/blake2b: fix 386, round 2
* core: log chain reorg/split metrics * core: report 1-block reorgs on the metrics too
- Move the existing tests from memorydb into a generalized testsuite that can be run by any ethdb backend implementation. - Add several more test cases to clarify some non-obvious nuances when implementing a custom ethdb backend, such as the behaviour of NewIteratorWithPrefix vs NewIteratorWithStart. - Add leveldb to the testsuite using in-memory storage for fast execution.
build: gomobile automaticall adds the ios tag, don't duplicate
This copies cli.printHelp but changes minwidth to 38. Custom flag code is improved to print the default value using cli.FlagStringer like all built-in flags do.
This change adds support for gzip encoding on HTTP responses. Gzip encoding is used when the client sets the 'accept-encoding: gzip' header. Original change by @brianosaurus, with fixes from @SjonHortensius.
core/vm: enable istanbul EIPs in the jump table
cmd, core, eth, les: support --override.istanbul
* Change chainId in genesis block to 8888 from 0 Change chainId in genesis block to 8888 from 0 per Moriteru in https://ethereum.stackexchange.com/a/28082/40230. * Replace 8888 with “<arbitrary positive integer>” Per PR review, replace Moriteru’s arbitrary positive integer 8888 with “<arbitrary positive integer>” in chainId field.
…20010) * les: wait all task routines before drop the peer * les: address comments * les: fix issue
eth: disallow overwrite files via admin.exportChain
internal/ethapi: implement fillTransaction
…eum#19933) Currently light.maxpeers is 100 - after this change it's 10 for non-servers. Fixes ethereum#19820
Dockerfile: expose GraphQL ports
* Accounts in alloc field must already exist Note that accounts in alloc field must already exist, as pointed out by Simeon Vanov in https://gettoshare.com/2017/10/30/how-to-use-genesis-json-alloc-property/ * Change wording per PR review comment * README: minor fixups
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
…8142) This should reduce the occurences of travis failures on MacOS Also fix some linter warnings
Package name See merge request NebulaAI-BlockChain/nbai-node!1
…into dev � Conflicts: � eth/config.go � node/defaults.go � params/bootnodes.go � params/config.go � tests/testdata
…020 at 11:19:06 am
set Constantinople Block to 3075000, which comes around January 15, 2020 at 11:19:06 am See merge request NebulaAI-BlockChain/nbai-node!2
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.