upgrade snow to 0.8.0 #2269
Closed
upgrade snow to 0.8.0 #2269
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
libp2p-dns requires a new feature in parity-multiaddr v0.11.2 namely Multiaddr::ends_with. libp2p-dns does not depend on parity-multiaddr directly but through libp2p-core. Prepare a new version of libp2p-core requiring at least parity-multiaddr v0.11.2 and update libp2p-dns to require libp2p-core v0.28.1.
Add notable users: - ipfs-embed. Rust IPFS implementation with a focus on being embeddable into rust applications - actyx, platform for writing manufacturing applications, based on rust-libp2p
…1999) * Implement /ipfs/id/push/1.0.0 alongside some refactoring. * Implement /ipfs/id/push/1.0.0, i.e. the ability to actively push information of the local peer to specific remotes. * Make the initial delay as well as the recurring delay for the periodic identification requests configurable, introducing `IdentifyConfig`. * Fix test. * Fix example. * Update protocols/identify/src/identify.rs Co-authored-by: Max Inden <mail@max-inden.de> * Update protocols/identify/src/identify.rs Co-authored-by: Max Inden <mail@max-inden.de> * Update versions and changelogs. Co-authored-by: Max Inden <mail@max-inden.de>
Remove `Deref` and `DerefMut` implementations previously dereferencing to the `NetworkBehaviour` on `Swarm`. Instead one can access the `NetworkBehaviour` via `Swarm::behaviour` and `Swarm::behaviour_mut`. Methods on `Swarm` can now be accessed directly, e.g. via `my_swarm.local_peer_id()`. Reasoning: Accessing the `NetworkBehaviour` of a `Swarm` through `Deref` and `DerefMut` instead of a method call is an unnecessary complication, especially for newcomers. In addition, `Swarm` is not a smart-pointer and should thus not make use of `Deref` and `DerefMut`, see documentation from the standard library below. > Deref should only be implemented for smart pointers to avoid confusion. https://doc.rust-lang.org/std/ops/trait.Deref.html
…2004) * Add configurable automatic push of listen addr changes. * Update changelog and cleanup.
Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
Co-authored-by: Max Inden <mail@max-inden.de>
…2026) * build(deps): update derive_builder requirement from 0.9.0 to 0.10.0 Updates the requirements on [derive_builder](https://github.com/colin-kiegel/rust-derive-builder) to permit the latest version. - [Release notes](https://github.com/colin-kiegel/rust-derive-builder/releases) - [Commits](colin-kiegel/rust-derive-builder@v0.9.0...v0.10.0) Signed-off-by: dependabot[bot] <support@github.com> * protocols/gossipsub/CHANGELOG: Add entry Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
This commit extends the ping example in `src/tutorial.rs, by walking a newcomer through the implementation of a simple ping node step-by-step, introducing all the core libp2p concepts along the way. With the ping tutorial in place, there is no need for the lengthy libp2p crate level introduction, which is thus removed with this commit. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
Co-authored-by: Max Inden <mail@max-inden.de>
…2033) Co-authored-by: Max Inden <mail@max-inden.de>
Instead of fully executing benchmarks, i.e. running multiple iterations, each measured and recorded, only test that they compile and run them with a single execution to make sure they work. The benefit is a reduced CI runtime. Flag documentation: > To test that the benchmarks run successfully without performing the measurement or analysis (eg. in a CI setting), use cargo test --benches. https://bheisler.github.io/criterion.rs/book/user_guide/command_line_options.html The above assumes that (a) the benchmark results from CI are likely noisy and thus (b) no one actually looks at the benchmark results.
…2045) Bumps [styfle/cancel-workflow-action](https://github.com/styfle/cancel-workflow-action) from 0.8.0 to 0.9.0. - [Release notes](https://github.com/styfle/cancel-workflow-action/releases) - [Commits](styfle/cancel-workflow-action@0.8.0...89f242e) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
With `rand` `v0.8.0` platform support changed [1] due to its upgrade to `getrandom` `v0.2`. With `getrandom` `v0.2` `wasm32-unknown-unknown` is no longer supported out of the box: > This crate fully supports the wasm32-wasi and wasm32-unknown-emscripten > targets. However, the wasm32-unknown-unknown target is not automatically > supported since, from the target name alone, we cannot deduce which JavaScript > interface is in use (or if JavaScript is available at all). > > Instead, if the "js" Cargo feature is enabled, this crate will assume that you > are building for an environment containing JavaScript, and will call the > appropriate methods. Both web browser (main window and Web Workers) and > Node.js environments are supported, invoking the methods described above using > the wasm-bindgen toolchain. > > This feature has no effect on targets other than wasm32-unknown-unknown. This commit drops support for wasm32-unknown-unknown in favor of the two more specific targets wasm32-wasi and wasm32-unknown-emscripten. Note on `resolver = "2"`: The new resolver is required to prevent features being mixed, more specifically to prevent libp2p-noise to build with the `ring-resolver` feature. See [3] for details. --- [1] https://github.com/rust-random/rand/blob/master/CHANGELOG.md#platform-support [2] https://docs.rs/getrandom/0.2.2/getrandom/#webassembly-support [3] https://doc.rust-lang.org/nightly/cargo/reference/features.html#feature-resolver-version-2
* Update yamux requirement from 0.8.0 to 0.9.0 Updates the requirements on [yamux](https://github.com/paritytech/yamux) to permit the latest version. - [Release notes](https://github.com/paritytech/yamux/releases) - [Changelog](https://github.com/paritytech/yamux/blob/develop/CHANGELOG.md) - [Commits](https://github.com/paritytech/yamux/commits) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
Co-authored-by: Max Inden <mail@max-inden.de>
Bumps [actions/cache](https://github.com/actions/cache) from v2.1.4 to v2.1.5. - [Release notes](https://github.com/actions/cache/releases) - [Commits](actions/cache@v2.1.4...1a9e213) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
mxinden
force-pushed
the
libp2p-noise-0.30
branch
from
054d512
to
aab2f66
Compare
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.
resolves #2231