Prague code merge [v1.13.15, v1.14.11] #3692
Annotations
1 error and 1 warning
commitlint (14.x, ubuntu-latest)
You have commit messages with errors
⧗ input: internal/ethapi: recap higher args.Gas with block GasLimit in DoEstimateGas (#29738)
* internal/ethapi: recap higher args.Gas with block GasLimit in DoEstimateGas
* internal/ethapi: fix gas estimator capping code
* internal/ethapi: fix test
* fix goimports lint (remove space)
---------
Co-authored-by: Péter Szilágyi <[email protected]>
✖ header must not be longer than 80 characters, current length is 84 [header-max-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/bnb-chain/bsc/tree/develop/docs/lint/commit.md
⧗ input: p2p: use netip.Addr where possible (#29891)
enode.Node was recently changed to store a cache of endpoint information. The IP address in the cache is a netip.Addr. I chose that type over net.IP because it is just better. netip.Addr is meant to be used as a value type. Copying it does not allocate, it can be compared with ==, and can be used as a map key.
This PR changes most uses of Node.IP() into Node.IPAddr(), which returns the cached value directly without allocating.
While there are still some public APIs left where net.IP is used, I have converted all code used internally by p2p/discover to the new types. So this does change some public Go API, but hopefully not APIs any external code actually uses.
There weren't supposed to be any semantic differences resulting from this refactoring, however it does introduce one: In package p2p/netutil we treated the 0.0.0.0/8 network (addresses 0.x.y.z) as LAN, but netip.Addr.IsPrivate() doesn't. The treatment of this particular IP address range is controversial, with some software supporting it and others not. IANA lists it as special-purpose and invalid as a destination for a long time, so I don't know why I put it into the LAN list. It has now been marked as special in p2p/netutil as well.
✖ body's lines must not be longer than 100 characters [body-max-line-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/bnb-chain/bsc/tree/develop/docs/lint/commit.md
⧗ input: cmd, core: prefetch reads too from tries if requested (#29807)
* cmd/utils, consensus/beacon, core/state: when configured via stub flag: prefetch all reads from account/storage tries, terminate prefetcher synchronously.
* cmd, core/state: fix nil panic, fix error handling, prefetch nosnap too
* core/state: expand prefetcher metrics for reads and writes separately
* cmd/utils, eth: fix noop collect witness flag
---------
Co-authored-by: Péter Szilágyi <[email protected]>
✖ body's lines must not be longer than 100 characters [body-max-line-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/bnb-chain/bsc/tree/develop/docs/lint/commit.md
⧗ input: core/state, eth/protocols, trie, triedb/pathdb: remove unused error from trie Commit (#29869)
* core/state, eth/protocols, trie, triedb/pathdb: remove unused error return from trie Commit
* move set back to account-trie-update block scoping for easier readability
* address review
* undo tests submodule change
* trie: panic if BatchSerialize returns an error in Verkle trie Commit
* trie: verkle comment nitpicks
---------
Co-authored-by: Péter Szilágyi <[email protected]>
✖ header must not be longer than 80 characters, current length is 94 [header-max-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/bnb-chain/bsc/tree/develop/docs/lint/commit.md
⧗ input: common: using `ParseUint` instead of `ParseInt` (#30020)
Since Decimal is defined as unsiged `uint64`, we should use `strconv.ParseUint` instead of `strconv.ParseInt` during unmarshalling.
---------
Co-authored-by: Martin Holst Swende <[email protected]>
✖ body's lines must not be longer than 100 characters [body-max-line-length]
✖ found 1 problems, 0 warnings
ⓘ Get help: https://github.com/bnb-chain/bsc/tree/develop/docs/lint/commit.md
|
commitlint (14.x, ubuntu-latest)
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-node@v3, actions/cache@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|