Update tree-states branch with changes from v5.1.0
#5388
Merged
Conversation
This file contains hidden or 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
* Add dependencies
* Run `apt update` before install.
* Delete ancient, unused HTTP docs
* Add a cli option for snapshot cache size * Remove junk * Make snapshot_cache module public * lint * Update docs
* Fix typo in `verify_payload_block_hash` * Make calculate_execution_block_hash public again
* Record the multiaddr for connected peers
* remove nat module and use libp2p upnp * update Cargo.lock * remove no longer used dependencies * restore nat module refactored * log successful mapping * only activate upnp if config enabled reduce logs to debug! * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * address review * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * Merge branch 'unstable' of https://github.com/sigp/lighthouse into libp2p-nat * address review
* remove exit-future usage, as it is non maintained, and replace with async-channel which is already in the repo. * Merge branch 'unstable' of https://github.com/sigp/lighthouse into remove-exit-future * Merge branch 'unstable' of https://github.com/sigp/lighthouse into remove-exit-future
* patch rust-yamux dep * improve libp2p connected peer metrics
* Caplin has joined the party * Fix typo
* Optimise no-op changes in VC API * Handle another no-op case * Merge remote-tracking branch 'origin/unstable' into opt-vc-patch-api
* Drop address_change_broadcast
* bump ethereum_serde_utils * cargo update
* Improve logging around score states * Improve logs also
* Fix duties override bug in VC * Use initial request efficiently * Prevent expired subscriptions by construction * Clean up selection proof logic * Add test
* fix lib.rs and tests.rs * update decode.rs * auto-delete in Cargo.lock * delete milagro in cargo.toml * remove milagro from makefile * remove milagro from the name * delete milagro in comment * delete milagro in cargo.toml * delete in /testing/ef_tests/cargo.toml * delete milagro in the logical OR * delete milagro in /lighthouse/src/main.rs * delete milagro in /crypto/bls/tests/tests.rs * delete milagro in comment * delete milagro in /testing//ef_test/src//cases/bls_eth_aggregate_pubkeys.rs * delete milagro * delete more in lib.rs * delete more in lib.rs * delete more in lib.rs * delete milagro in /crypto/bls/src/lib.rs * delete milagro in crypto/bls/src/mod.rs * delete milagro.rs
* Fix block v3 header decoding
* changed to is_empty() and removed WARN * added log argument * fix: issue 5288
* Code improvements * Fix gossipsub tests * Merge latest unstable * Differentiate errors and better scoring * Attempt to publish to mesh_n peers
* Handle fork boundaries * Merge latest unstable * Topic subscription fix
* Update and pin all actions to a modern release
* Fix tests * Merge branch 'unstable' into unclog-channels * Avoid reallocations * Reduce subscription load on beacon node
* Merge latest unstable * Reduce diff * Reduce logic, discover up to max peers * Peer discovery for Natd peers
* Merge branch 'unstable' into feature/explicit-peers * Merge latest unstable * refactor: remove explicit-peers flag, mark trusted peers as explicit instead * feat(beacon_node): add explicit peers to GossipSub, mark as trusted * feat(beacon_node): add explicit peers cli + config
* Optimise concurrent block production
* Address review comments * Downgrade log for by_root requests
* Bump versions
michaelsproul
added
work-in-progress
Member
Author
|
Idk what's wrong with the macOS build. Doesn't seem related, so I'll merge this. |
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
10 participants
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.
Proposed Changes
Merge latest
unstabledown intotree-statesin prep for v5.1.111-expAdditional Info
This PR shouldn't be squashed.