fluencelabs/rust-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/rust-libp2p synced 2025-05-15 04:11:19 +00:00
Code Issues Projects Releases Wiki Activity
rust-libp2p/protocols/request-response/CHANGELOG.md

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

207 lines
5.3 KiB
Markdown
Raw Normal View History

chore: Bump libp2p-swarm dependents (#3225) Follow-up to https://github.com/libp2p/rust-libp2p/pull/3170#issuecomment-1344847006
2022-12-12 12:30:23 +01:00
# 0.24.0 [unreleased]
deps!: Update multiaddr & multihash to 0.17.0 (#3196)
2022-12-20 09:52:08 +01:00
- Update to `libp2p-core` `v0.39.0`.
refactor(request-response): revise public API to follow naming convention (#3159)
2022-12-13 12:11:42 +00:00
- Rename types as per [discussion 2174].
`RequestResponse` has been renamed to `Behaviour`.
The `RequestResponse` prefix has been removed from various types like `RequestResponseEvent`.
Users should prefer importing the request_response protocol as a module (`use libp2p::request_response;`),
and refer to its types via `request_response::`. For example: `request_response::Behaviour` or `request_response::Event`.
See [PR 3159].
chore: Bump libp2p-swarm dependents (#3225) Follow-up to https://github.com/libp2p/rust-libp2p/pull/3170#issuecomment-1344847006
2022-12-12 12:30:23 +01:00
- Update to `libp2p-swarm` `v0.42.0`.
refactor(request-response): revise public API to follow naming convention (#3159)
2022-12-13 12:11:42 +00:00
[discussion 2174]: https://github.com/libp2p/rust-libp2p/discussions/2174
[PR 3159]: https://github.com/libp2p/rust-libp2p/pull/3159
chore: Prepare rust-libp2p v0.50.0 release (#3163)
2022-11-25 10:37:55 +01:00
# 0.23.0
*: Don't leak `prost` dependency in error types (#3058) With the current design, a major version bump of `prost` leaks into all consumers of `prost-codec`.
2022-11-02 23:02:21 +11:00
- Update to `libp2p-core` `v0.38.0`.
- Update to `libp2p-swarm` `v0.41.0`.
swarm/behaviour: Replace `inject_*` with `on_event` (#3011)
2022-11-17 09:28:40 +00:00
- Replace `RequestResponse`'s `NetworkBehaviour` implemention `inject_*` methods with the new `on_*` methods.
See [PR 3011].
swarm/handler: replace inject_* methods (#3085) Previously, we had one callback for each kind of message that a `ConnectionHandler` would receive from either its `NetworkBehaviour` or the connection itself. With this patch, we combine these functions, resulting in two callbacks: - `on_behaviour_event` - `on_connection_event` Resolves #3080.
2022-11-17 17:19:36 +00:00
- Replace `RequestResponseHandler`'s `ConnectionHandler` implemention `inject_*` methods
with the new `on_*` methods. See [PR 3085].
.github/workflows: Refactor CI jobs (#3090) We refactor our continuous integration workflow with the following goals in mind: - Run as few jobs as possible - Have the jobs finish as fast as possible - Have the jobs redo as little work as possible There are only so many jobs that GitHub Actions will run in parallel. Thus, it makes sense to not create massive matrices but instead group things together meaningfully. The new `test` job will: - Run once for each crate - Ensure that the crate compiles on its specified MSRV - Ensure that the tests pass - Ensure that there are no semver violations This is an improvement to before because we are running all of these in parallel which speeds up execution and highlights more errors at once. Previously, tests run later in the pipeline would not get run at all until you make sure the "first" one passes. We also previously did not verify the MSRV of each crate, making the setting in the `Cargo.toml` rather pointless. The new `cross` job supersedes the existing `wasm` job. This is an improvement because we now also compile the crate for windows and MacOS. Something that wasn't checked before. We assume that checking MSRV and the tests under Linux is good enough. Hence, this job only checks for compile-errors. The new `feature_matrix` ensures we compile correctly with certain feature combinations. `libp2p` exposes a fair few feature-flags. Some of the combinations are worth checking independently. For the moment, this concerns only the executor related transports together with the executor flags but this list can easily be extended. The new `clippy` job runs for `stable` and `beta` rust. Clippy gets continuously extended with new lints. Up until now, we would only learn about those as soon as a new version of Rust is released and CI would run the new lints. This leads to unrelated failures in CI. Running clippy on with `beta` Rust gives us a heads-up of 6 weeks before these lints land on stable. Fixes #2951.
2022-11-18 22:04:16 +11:00
- Update `rust-version` to reflect the actual MSRV: 1.62.0. See [PR 3090].
swarm/handler: replace inject_* methods (#3085) Previously, we had one callback for each kind of message that a `ConnectionHandler` would receive from either its `NetworkBehaviour` or the connection itself. With this patch, we combine these functions, resulting in two callbacks: - `on_behaviour_event` - `on_connection_event` Resolves #3080.
2022-11-17 17:19:36 +00:00
[PR 3085]: https://github.com/libp2p/rust-libp2p/pull/3085
swarm/behaviour: Replace `inject_*` with `on_event` (#3011)
2022-11-17 09:28:40 +00:00
[PR 3011]: https://github.com/libp2p/rust-libp2p/pull/3011
.github/workflows: Refactor CI jobs (#3090) We refactor our continuous integration workflow with the following goals in mind: - Run as few jobs as possible - Have the jobs finish as fast as possible - Have the jobs redo as little work as possible There are only so many jobs that GitHub Actions will run in parallel. Thus, it makes sense to not create massive matrices but instead group things together meaningfully. The new `test` job will: - Run once for each crate - Ensure that the crate compiles on its specified MSRV - Ensure that the tests pass - Ensure that there are no semver violations This is an improvement to before because we are running all of these in parallel which speeds up execution and highlights more errors at once. Previously, tests run later in the pipeline would not get run at all until you make sure the "first" one passes. We also previously did not verify the MSRV of each crate, making the setting in the `Cargo.toml` rather pointless. The new `cross` job supersedes the existing `wasm` job. This is an improvement because we now also compile the crate for windows and MacOS. Something that wasn't checked before. We assume that checking MSRV and the tests under Linux is good enough. Hence, this job only checks for compile-errors. The new `feature_matrix` ensures we compile correctly with certain feature combinations. `libp2p` exposes a fair few feature-flags. Some of the combinations are worth checking independently. For the moment, this concerns only the executor related transports together with the executor flags but this list can easily be extended. The new `clippy` job runs for `stable` and `beta` rust. Clippy gets continuously extended with new lints. Up until now, we would only learn about those as soon as a new version of Rust is released and CI would run the new lints. This leads to unrelated failures in CI. Running clippy on with `beta` Rust gives us a heads-up of 6 weeks before these lints land on stable. Fixes #2951.
2022-11-18 22:04:16 +11:00
[PR 3090]: https://github.com/libp2p/rust-libp2p/pull/3090
swarm/behaviour: Replace `inject_*` with `on_event` (#3011)
2022-11-17 09:28:40 +00:00
*: Prepare v0.49.0 (#2931)
2022-10-14 15:30:16 +01:00
# 0.22.0
build(deps): Bump rand to 0.8 and quickcheck to 1 (#2857) Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Max Inden <mail@max-inden.de>
2022-09-22 12:48:32 +04:00
- Bump rand to 0.8 and quickcheck to 1. See [PR 2857].
*: Remove default features from all crates (#2918) Remove default features. You need to enable required features explicitly now. As a quick workaround, you may want to use the new `full` feature which activates all features.
2022-09-30 01:32:22 +10:00
- Update to `libp2p-core` `v0.37.0`.
- Update to `libp2p-swarm` `v0.40.0`.
build(deps): Bump rand to 0.8 and quickcheck to 1 (#2857) Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Max Inden <mail@max-inden.de>
2022-09-22 12:48:32 +04:00
[PR 2857]: https://github.com/libp2p/rust-libp2p/pull/2857
*: Prepare v0.48.0 (#2869)
2022-09-07 09:44:51 +02:00
# 0.21.0
swarm/behaviour: Remove deprecated NetworkBehaviourEventProcess (#2840) Removes the `NetworkBehaviourEventProcess` and all its associated logic. See deprecation pull request https://github.com/libp2p/rust-libp2p/pull/2784. Find rational in https://github.com/libp2p/rust-libp2p/pull/2751.
2022-08-26 07:08:33 +02:00
- Update to `libp2p-swarm` `v0.39.0`.
core/: Introduce `rsa` feature flag to avoid `ring` dependency (#2860) - Introduce `rsa` feature flag to `libp2p-core`. - Expose `rsa` feature in `libp2p`. - Add `rsa` feature to `libp2p` `default`.
2022-09-07 09:16:22 +03:00
- Update to `libp2p-core` `v0.36.0`.
*: Prepare v0.47.0 (#2830)
2022-08-22 05:14:04 +02:00
# 0.20.0
swarm/: Set default dial concurrency factor to 8 (#2741)
2022-07-07 04:20:03 -05:00
- Update to `libp2p-swarm` `v0.38.0`.
core/muxing: Flatten `StreamMuxer` interface to `poll_{inbound,outbound,address_change,close}` (#2724) Instead of having a mix of `poll_event`, `poll_outbound` and `poll_close`, we flatten the entire interface of `StreamMuxer` into 4 individual functions: - `poll_inbound` - `poll_outbound` - `poll_address_change` - `poll_close` This design is closer to the design of other async traits like `AsyncRead` and `AsyncWrite`. It also allows us to delete the `StreamMuxerEvent`.
2022-07-18 04:20:11 +01:00
- Update to `libp2p-core` `v0.35.0`.
*: Prepare v0.46.0 (#2730)
2022-07-05 13:09:58 +02:00
# 0.19.0
core/muxing: Force `StreamMuxer::Substream` to implement `Async{Read,Write}` (#2707) Co-authored-by: Max Inden <mail@max-inden.de>
2022-06-23 13:52:11 +02:00
- Update to `libp2p-core` `v0.34.0`.
- Update to `libp2p-swarm` `v0.37.0`.
*: Prepare v0.45.0 (#2662)
2022-05-31 13:12:53 +02:00
# 0.18.0
{core,swarm}/: Don't require `Transport: Clone` and take `&mut` (#2529) Previously `libp2p-swarm` required a `Transport` to be `Clone`. Methods on `Transport`, e.g. `Transport::dial` would take ownership, requiring e.g. a `Clone::clone` before calling `Transport::dial`. The requirement of `Transport` to be `Clone` is no longer needed in `libp2p-swarm`. E.g. concurrent dialing can be done without a clone per dial. This commit removes the requirement of `Clone` for `Transport` in `libp2p-swarm`. As a follow-up methods on `Transport` no longer take ownership, but instead a mutable reference (`&mut self`). On the one hand this simplifies `libp2p-swarm`, on the other it simplifies implementations of `Transport`.
2022-04-06 20:23:16 +02:00
- Update to `libp2p-core` `v0.33.0`.
- Update to `libp2p-swarm` `v0.36.0`.
*: Prepare libp2p v0.44.0 (#2604)
2022-04-04 18:27:41 +02:00
# 0.17.0
swarm/src/behaviour: Remove Send bound from NetworkBehaviour (#2535) The bound is no longer needed across the libp2p-XXX crates. Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-28 10:27:58 +01:00
- Update to `libp2p-swarm` `v0.35.0`.
*: Prepare v0.43.0 (#2531)
2022-02-22 14:05:19 +01:00
# 0.16.0 [2022-02-22]
*: Update multihash and multiaddr (#2469) Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-03 16:38:41 +00:00
- Update to `libp2p-core` `v0.32.0`.
- Update to `libp2p-swarm` `v0.34.0`.
swarm/src/behaviour: Merge inject_* paired methods (#2445) Co-authored-by: Max Inden <mail@max-inden.de>
2022-02-09 10:08:28 -05:00
- Merge NetworkBehaviour's inject_\* paired methods (see PR 2445).
[PR 2445]: https://github.com/libp2p/rust-libp2p/pull/2445
*: Prepare v0.42.0 (#2440)
2022-01-27 11:29:09 +01:00
# 0.15.0 [2022-01-27]
swarm/: Patch reporting on banned peer connections (#2350) Don't report events of a connection to the `NetworkBehaviour`, if connection has been established while the remote peer was banned. Among other guarantees this upholds that `NetworkBehaviour::inject_event` is never called without a previous `NetworkBehaviour::inject_connection_established` for said connection. Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 10:48:12 -05:00
- Update dependencies.
protocols/request-response: Remove unused crate lru (#2358)
2021-11-26 18:08:16 +01:00
- Remove unused `lru` crate (see [PR 2358]).
*: Migrate to Rust 2021 edition (#2339) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 09:34:58 -07:00
- Migrate to Rust edition 2021 (see [PR 2339]).
[PR 2339]: https://github.com/libp2p/rust-libp2p/pull/2339
protocols/request-response: Remove unused crate lru (#2358)
2021-11-26 18:08:16 +01:00
[PR 2358]: https://github.com/libp2p/rust-libp2p/pull/2358
*: Migrate to Rust 2021 edition (#2339) Co-authored-by: Max Inden <mail@max-inden.de>
2021-11-26 09:34:58 -07:00
*: Prepare v0.41.0 (#2342)
2021-11-16 16:39:42 +01:00
# 0.14.0 [2021-11-16]
*: Enable libp2p to run via wasm32-unknown-unknown in the browser (#2320) Changes needed to get libp2p to run via `wasm32-unknown-unknown` in the browser (both main thread and inside web workers). Replaces wasm-timer with futures-timer and instant. Co-authored-by: Oliver Wangler <oliver@wngr.de>
2021-10-30 12:41:30 +02:00
- Use `instant` instead of `wasm-timer` (see [PR 2245]).
swarm/: Enable advanced dialing requests (#2317) Enable advanced dialing requests both on `Swarm` and via `NetworkBehaviourAction`. Users can now trigger a dial with a specific set of addresses, optionally extended via `NetworkBehaviour::addresses_of_peer`. In addition the whole process is now modelled in a type safe way via the builder pattern. Example of a `NetworkBehaviour` requesting a dial to a specific peer with a set of addresses additionally extended through `NetworkBehaviour::addresses_of_peer`: ```rust NetworkBehaviourAction::Dial { opts: DialOpts::peer_id(peer_id) .condition(PeerCondition::Always) .addresses(addresses) .extend_addresses_through_behaviour() .build(), handler, } ``` Example of a user requesting a dial to an unknown peer with a single address via `Swarm`: ```rust swarm1.dial( DialOpts::unknown_peer_id() .address(addr2.clone()) .build() ) ```
2021-11-15 14:17:23 +01:00
- Update dependencies.
*: Enable libp2p to run via wasm32-unknown-unknown in the browser (#2320) Changes needed to get libp2p to run via `wasm32-unknown-unknown` in the browser (both main thread and inside web workers). Replaces wasm-timer with futures-timer and instant. Co-authored-by: Oliver Wangler <oliver@wngr.de>
2021-10-30 12:41:30 +02:00
[PR 2245]: https://github.com/libp2p/rust-libp2p/pull/2245
Merge branch 'libp2p/v0.40' into master (#2324) * *: Prepare v0.40.0 release (#2323) * Cargo.toml: Remove rc suffix
2021-11-02 20:40:48 +01:00
# 0.13.0 [2021-11-01]
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
*: Make libp2p-core default features optional (#2181) Co-authored-by: Max Inden <mail@max-inden.de>
2021-08-18 12:08:45 +02:00
- Make default features of `libp2p-core` optional.
[PR 2181](https://github.com/libp2p/rust-libp2p/pull/2181)
to/into consistency for PublicKey and PeerId (#2145) - Change `PublicKey::into_protobuf_encoding` to `PublicKey::to_protobuf_encoding`. - Change `PublicKey::into_peer_id` to `PublicKey::to_peer_id`. - Change `PeerId::from_public_key(PublicKey)` to `PeerId::from_public_key(&PublicKey)`. - Add `From<&PublicKey> for PeerId`. Co-authored-by: Max Inden <mail@max-inden.de>
2021-07-22 22:34:13 +02:00
- Update dependencies.
core/: Remove TInEvent and TOutEvent (#2183) TInEvent and TOutEvent are implied through THandler and thus superflucious. Both are removed in favor of a derivation through THandler.
2021-08-11 12:41:28 +02:00
- Manually implement `Debug` for `RequestResponseHandlerEvent` and
`RequestProtocol`. See [PR 2183].
protocols/request-response: Remove throttled module (#2236) Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Max Inden <mail@max-inden.de>
2021-09-25 18:18:06 +02:00
- Remove `RequestResponse::throttled` and the `throttled` module.
See [PR 2236].
core/: Remove TInEvent and TOutEvent (#2183) TInEvent and TOutEvent are implied through THandler and thus superflucious. Both are removed in favor of a derivation through THandler.
2021-08-11 12:41:28 +02:00
[PR 2183]: https://github.com/libp2p/rust-libp2p/pull/2183
protocols/request-response: Remove throttled module (#2236) Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Max Inden <mail@max-inden.de>
2021-09-25 18:18:06 +02:00
[PR 2236]: https://github.com/libp2p/rust-libp2p/pull/2236
core/: Remove TInEvent and TOutEvent (#2183) TInEvent and TOutEvent are implied through THandler and thus superflucious. Both are removed in favor of a derivation through THandler.
2021-08-11 12:41:28 +02:00
*: Prepare v0.39.0 release (#2132)
2021-07-12 21:24:58 +02:00
# 0.12.0 [2021-07-12]
*: Use upstream multiaddr crate (#2075) Use multiaddr instead of parity-multiaddr, removing the latter from the repository.
2021-05-27 14:04:33 +02:00
- Update dependencies.
*: Prepare v0.37.0 release (#2049)
2021-04-13 20:15:15 +02:00
# 0.11.0 [2021-04-13]
swarm/src/lib: Remove Deref and DerefMut impls on Swarm (#1995) 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
2021-03-18 14:55:33 +01:00
- Update `libp2p-swarm`.
Implement std::error::Error for InboundFailure and OutboundFailure (#2033) Co-authored-by: Max Inden <mail@max-inden.de>
2021-04-08 21:14:34 +10:00
- Implement `std::error::Error` for `InboundFailure` and `OutboundFailure` [PR
2033](https://github.com/libp2p/rust-libp2p/pull/2033).
swarm/src/lib: Remove Deref and DerefMut impls on Swarm (#1995) 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
2021-03-18 14:55:33 +01:00
*: Prepare v0.36.0 release
2021-03-17 15:28:13 +01:00
# 0.10.0 [2021-03-17]
[swarm] Remove substream-specific protocol negotiation version. (#1962) * Remove substream-specific protocol negotiation version. Remove the option for a substream-specific multistream select protocol override. The override at this granularity is no longer deemed useful, in particular because it can usually not be configured for existing protocols like `libp2p-kad` and others. There is a `Swarm`-scoped configuration for this version available since [1858](https://github.com/libp2p/rust-libp2p/pull/1858). * Update protocol crate versions and changelogs. * Clean up documentation.
2021-02-25 11:35:52 +01:00
- Update `libp2p-swarm`.
protocols/request-response: Update CHANGELOG.md
2021-03-09 17:54:23 +01:00
- Close stream even when no response has been sent.
[PR 1987](https://github.com/libp2p/rust-libp2p/pull/1987).
*: Require smallvec >= 1.6.1 (#1994) Versions <1.6.1 are vulnerable to a buffer overflow. See https://rustsec.org/advisories/RUSTSEC-2021-0003.html for details.
2021-03-15 12:31:21 +01:00
- Update dependencies.
Prepare v0.35 (#1957)
2021-02-15 20:06:50 +01:00
# 0.9.1 [2021-02-15]
*: Update changelogs and cargo tomls for req-resp patch
2021-01-21 14:36:58 +01:00
protocols/request-response: Add forgotten changelog entry
2021-01-21 15:40:26 +01:00
- Make `is_pending_outbound` return true on pending connection.
[PR 1928](https://github.com/libp2p/rust-libp2p/pull/1928).
Update unsigned-varint and asynchronous-codec (#1946) * Update unsigned-varint requirement from 0.6 to 0.7 Updates the requirements on [unsigned-varint](https://github.com/paritytech/unsigned-varint) to permit the latest version. - [Release notes](https://github.com/paritytech/unsigned-varint/releases) - [Changelog](https://github.com/paritytech/unsigned-varint/blob/master/CHANGELOG.md) - [Commits](https://github.com/paritytech/unsigned-varint/compare/v0.6.0...v0.7.0) Signed-off-by: dependabot[bot] <support@github.com> * *: Update to asynchronous-codec v0.6 * transports/plaintext: Use Framed::into_parts * *: Update cargo tomls and changelogs Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2021-02-13 20:15:14 +01:00
- Update dependencies.
*: Prepare v0.34.0 release (#1918) Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2021-01-12 20:33:43 +01:00
# 0.9.0 [2021-01-12]
*: Update changelogs and cargo tomls for new reqresp release
2021-01-04 18:51:05 +01:00
*: Switch futures_codec to asynchronous-codec (#1908) `futures-codec` has not been updated in the recent months. It still depends on `bytes` `v0.5` preventing all downstream dependencies to upgrade to `bytes` `v1.0`. This commit replaces `futures_codec` in favor of `asynchronous-codec` The latter is a fully upgraded fork of the former. In addition this commit upgrades: - bytes to v1 - unsigned-varint to v0.6.0 - prost to v0.7
2021-01-12 12:48:37 +01:00
- Update dependencies.
*: Update changelogs and cargo tomls for new reqresp release
2021-01-04 18:51:05 +01:00
- Re-export `throttled`-specific response channel. [PR
1902](https://github.com/libp2p/rust-libp2p/pull/1902).
*CHANGELOG.md: Prepare v0.33.0 release (#1895)
2020-12-18 10:03:20 +01:00
# 0.8.0 [2020-12-17]
Stack allocated PeerId (#1874) * Stack allocate PeerId. * Update stuff. * Upgrade rusttls to fix build. * Remove unnecessary manual implementations. * Remove PeerId::into_bytes. * Remove bytes dependency. * Perform some cleanup. * Use Into<kbucket::Key<K>>. * Update versions and changelogs. * Fix PR link. * Fix benchmarks. Co-authored-by: Roman S. Borschel <roman@parity.io>
2020-12-15 14:40:39 +01:00
- Update `libp2p-swarm` and `libp2p-core`.
protocols/request-response: Emit InboundFailure::ConnectionClosed (#1886) A user of libp2p-request-response is guaranteed to receive an additional event after receiving a request via `RequestResponseEvent::Message`. After receiving the request: - If the user responds in time and the connection is still alive, the user can expect a `ResponseSent`. - If the user drops the response channel, the user can expect an `InboundFailure::ResponseOmission`. - If the user does not respond in time, the user can expect an `InboundFailure::Timeout`. Thus far the user did not receive an event when the connection to the peer closes. With this commit: - If the connection to the peer closes before the users calls `send_response` or after the user calls `send_response` but before the response can be send on the network, the user can expect an `InboundFailure::ConnectionClosed`.
2020-12-16 16:03:35 +01:00
- Emit `InboundFailure::ConnectionClosed` for inbound requests that failed due
to the underlying connection closing.
[PR 1886](https://github.com/libp2p/rust-libp2p/pull/1886).
protocols/request-response: Derive Clone for {Inbound,Outbound}Failure (#1891)
2020-12-16 16:38:45 +01:00
- Derive Clone for `InboundFailure` and `Outbound}Failure`.
[PR 1891](https://github.com/libp2p/rust-libp2p/pull/1891)
Prepare v0.32 (#1879)
2020-12-08 12:07:20 +01:00
# 0.7.0 [2020-12-08]
[request-response] Refine success & error reporting for inbound requests. (#1867) * Refine error reporting for inbound request handling. At the moment one can neither get confirmation when a response has been sent on the underlying transport, nor is one aware of response omissions. The latter was originally intended as a feature for support of one-way protocols, which seems like a bad idea in hindsight. The lack of notification for sent responses may prohibit implementation of some request-response protocols that need to ensure a happens-before relation between sending a response and a subsequent request, besides uses for collecting statistics. Even with these changes, there is no active notification for failed inbound requests as a result of connections unexpectedly closing, as is the case for outbound requests. Instead, for pending inbound requests this scenario can be identified if necessary by the absense of both `InboundFailure` and `ResponseSent` events for a particular previously received request. Interest in this situation is not expected to be common and would otherwise require explicitly tracking all inbound requests in the `RequestResponse` behaviour, which would be a pity. `RequestResponse::send_response` now also synchronously returns an error if the inbound upgrade handling the request has been aborted, due to timeout or closing of the connection, giving more options for graceful error handling for inbound requests. As an aside, the `Throttled` wrapper now no longer emits inbound or outbound error events occurring in the context of sending credit requests or responses. This is in addition to not emitting `ResponseSent` events for ACK responses of credit grants. * Update protocols/request-response/src/lib.rs Co-authored-by: Max Inden <mail@max-inden.de> * Address some minor clippy warnings. (#1868) * Track pending credit request IDs. In order to avoid emitting events relating to credit grants or acks on the public API. The public API should only emit events relating to the actual requests and responses sent by client code. * Small cleanup * Cleanup * Update versions and changelogs. * Unreleased Co-authored-by: Max Inden <mail@max-inden.de>
2020-12-07 13:07:47 +01:00
- Refine emitted events for inbound requests, introducing
the `ResponseSent` event and the `ResponseOmission`
inbound failures. This effectively removes previous
support for one-way protocols without responses.
[PR 1867](https://github.com/libp2p/rust-libp2p/pull/1867).
Prepare release of `libp2p-v0.31` and all unreleased sub-crates. (#1857) * Prepare v0.31 * Update core-derive * Update minimum multiaddr patch version in libp2p crate.
2020-11-25 15:30:13 +01:00
# 0.6.0 [2020-11-25]
feat: upgrade multihash (#1792) * feat: upgrade to multihash 0.13 `multihash` changes a lot internally, it is using stack allocation instead of heap allocation. This leads to a few limitations in regards on how `Multihash` can be used. Therefore `PeerId` is now using a `Bytes` internally so that only minimal changes are needed. * Update versions and changelogs. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> Co-authored-by: Roman S. Borschel <roman@parity.io>
2020-11-17 11:15:20 +01:00
- Update `libp2p-swarm` and `libp2p-core`.
*: Update changelogs to release v0.30.0 (#1829) * *: Update changelogs to release v0.30.0 * muxers/mplex/CHANGELOG: Reference pull request * misc/multistream-select/CHANGELOG: Update date
2020-11-09 17:46:07 +01:00
# 0.5.0 [2020-11-09]
Remove ConnectionInfo trait (#1813) In all cases, we pass the PeerId directly as the connection info. The flexbility of doing something different here was originally envisioned but turned out to be never needed. For reference see: https://github.com/libp2p/rust-libp2p/issues/1798#issuecomment-714526056 Co-authored-by: Max Inden <mail@max-inden.de>
2020-10-31 01:51:27 +11:00
- Update dependencies.
Prepare release. (#1797)
2020-10-16 20:36:47 +02:00
# 0.4.0 [2020-10-16]
Update minicbor requirement from 0.5 to 0.6 (#1772) * Update minicbor requirement from 0.5 to 0.6 Updates the requirements on [minicbor](https://gitlab.com/twittner/minicbor) to permit the latest version. - [Release notes](https://gitlab.com/twittner/minicbor/tags) - [Commits](https://gitlab.com/twittner/minicbor/compare/minicbor-v0.5.0...minicbor-v0.6.0) Signed-off-by: dependabot[bot] <support@github.com> * *: Update changelogs and cargo tomls Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Max Inden <mail@max-inden.de>
2020-09-23 21:28:15 +02:00
- Update dependencies.
Prepare release(s). (#1738)
2020-09-09 12:20:25 +02:00
# 0.3.0 [2020-09-09]
Add `ProtocolsHandler::InboundOpenInfo`. (#1714) * Add `ProtocolsHandler::InboundOpenInfo`. * Update swarm/src/protocols_handler/multi.rs Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> * Update CHANGELOGs and versions. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2020-08-23 16:57:20 +02:00
Update request-response changelog.
2020-09-07 17:25:15 +02:00
- Add support for opt-in request-based flow-control to any
Add back the LRU cache to `Throttled`. (#1731) * Restore `RequestResponse::throttled`. In contrast to the existing "throttled" approach this PR adds back- pressure to the protocol without requiring pre-existing knowledge of all nodes about their limits. It adds small, CBOR-encoded headers to the actual payload data. Extra credit messages communicate back to the sender how many more requests it is allowed to send. * Remove some noise. * Resend credit grant after connection closed. Should an error in some lower layer cause a connection to be closed, our previously sent credit grant may not have reached the remote peer. Therefore, pessimistically, a credit grant is resent whenever a connection is closed. The remote ignores duplicate grants. * Remove inbound/outbound tracking per peer. * Send ACK as response to duplicate credit grants. * Simplify. * Fix grammar. * Incorporate review feedback. - Remove `ResponseSent` which was a leftover from previous attemps and issue a credit grant immediately in `send_response`. - Only resend credit grants after a connection is closed if we are still connected to this peer. * Move codec/header.rs to throttled/codec.rs. * More review suggestions. * Generalise `ProtocolWrapper` and use shorter prefix. * Update protocols/request-response/src/lib.rs Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> * Update protocols/request-response/src/throttled.rs Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> * Update protocols/request-response/src/throttled.rs Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> * Minor comment changes. * Limit max. header size to 8KiB * Always construct initial limit with 1. Since honest senders always assume a send budget of 1 and wait for credit afterwards, setting the default limit to a higher value can only become effective after informing the peer about it which means leaving `max_recv` at 1 and setting `next_max` to the desired value. * Use LRU cache to keep previous peer infos. Peers may send all their requests, reconnect and send again all their requests, starting from a fresh budget. The LRU cache keeps the peer information around and reuses it when the peer reconnects, continuing with the previous remaining limit. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2020-09-09 11:04:20 +02:00
request-response protocol via `RequestResponse::throttled()`.
Update request-response changelog.
2020-09-07 17:25:15 +02:00
[PR 1726](https://github.com/libp2p/rust-libp2p/pull/1726).
Set development versions appropriately and update changelogs.
2020-09-03 12:31:04 +02:00
- Update `libp2p-swarm` and `libp2p-core`.
Add `ProtocolsHandler::InboundOpenInfo`. (#1714) * Add `ProtocolsHandler::InboundOpenInfo`. * Update swarm/src/protocols_handler/multi.rs Co-authored-by: Roman Borschel <romanb@users.noreply.github.com> * Update CHANGELOGs and versions. Co-authored-by: Roman Borschel <romanb@users.noreply.github.com>
2020-08-23 16:57:20 +02:00
*: Prepare v0.24.0 release (#1713) * */CHANGELOG: Update dates * Cargo.toml: Update to 0.24.0
2020-08-18 17:04:34 +02:00
# 0.2.0 [2020-08-18]
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
Fix connection keep-alive for request-response. (#1700)
2020-08-13 13:13:23 +02:00
- Fixed connection keep-alive, permitting connections to close due
to inactivity.
[core/swarm] Emit events for active connection close and fix `disconnect()`. (#1619) * Emit events for active connection close and fix `disconnect()`. The `Network` does currently not emit events for actively closed connections, e.g. via `EstablishedConnection::close` or `ConnectedPeer::disconnect()`. As a result, when actively closing connections, there will be `ConnectionEstablished` events emitted without eventually a matching `ConnectionClosed` event. This seems undesirable and has the consequence that the `Swarm::ban_peer_id` feature in `libp2p-swarm` does not result in appropriate calls to `NetworkBehaviour::inject_connection_closed` and `NetworkBehaviour::inject_disconnected`. Furthermore, the `disconnect()` functionality in `libp2p-core` is currently broken as it leaves the `Pool` in an inconsistent state. This commit does the following: 1. When connection background tasks are dropped (i.e. removed from the `Manager`), they always terminate immediately, without attempting an orderly close of the connection. 2. An orderly close is sent to the background task of a connection as a regular command. The background task emits a `Closed` event before terminating. 3. `Pool::disconnect()` removes all connection tasks for the affected peer from the `Manager`, i.e. without an orderly close, thereby also fixing the discovered state inconsistency due to not removing the corresponding entries in the `Pool` itself after removing them from the `Manager`. 4. A new test is added to `libp2p-swarm` that exercises the ban/unban functionality and places assertions on the number and order of calls to the `NetworkBehaviour`. In that context some new testing utilities have been added to `libp2p-swarm`. This addresses https://github.com/libp2p/rust-libp2p/issues/1584. * Update swarm/src/lib.rs Co-authored-by: Toralf Wittner <tw@dtex.org> * Incorporate some review feedback. * Adapt to changes in master. * More verbose panic messages. * Simplify There is no need for a `StartClose` future. * Fix doc links. * Further small cleanup. * Update CHANGELOGs and versions. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-08-04 11:30:09 +02:00
- Bump `libp2p-core` and `libp2p-swarm` dependencies.
[request-response] Close substream after writing request/response. (#1660) * Close substream after writing request/response. * Update protocols/request-response/src/handler/protocol.rs Co-authored-by: Thomas Eizinger <thomas@eizinger.io> Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
2020-07-13 12:35:32 +02:00
# 0.1.1
- Always properly `close()` the substream after sending requests and
responses in the `InboundUpgrade` and `OutboundUpgrade`. Otherwise this is
left to `RequestResponseCodec::write_request` and `RequestResponseCodec::write_response`,
which can be a pitfall and lead to subtle problems (see e.g.
https://github.com/libp2p/rust-libp2p/pull/1606).
Add libp2p-request-response protocol. (#1596) * Add the libp2p-request-response protocol. This crate provides a generic implementation for request/response protocols, whereby each request is sent on a new substream. * Fix OneShotHandler usage in floodsub. * Custom ProtocolsHandler and multiple protocols. 1. Implement a custom ProtocolsHandler instead of using the OneShotHandler for better control and error handling. In particular, all request/response sending/receiving is kept in the substreams upgrades and thus the background task of a connection. 2. Support multiple protocols (usually protocol versions) with a single `RequestResponse` instance, with configurable inbound/outbound support. * Small doc clarification. * Remove unnecessary Sync bounds. * Remove redundant Clone constraint. * Update protocols/request-response/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> * Update dev-dependencies. * Update Cargo.tomls. * Add changelog. * Remove Sync bound from RequestResponseCodec::Protocol. Apparently the compiler just needs some help with the scope of borrows, which is unfortunate. * Try async-trait. * Allow checking whether a ResponseChannel is still open. Also expand the commentary on `send_response` to indicate that responses may be discard if they come in too late. * Add `RequestResponse::is_pending`. As an analogue of `ResponseChannel::is_open` for outbound requests. * Revert now unnecessary changes to the OneShotHandler. Since `libp2p-request-response` is no longer using it. * Update CHANGELOG for libp2p-swarm. Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-06-29 17:08:40 +02:00
# 0.1.0
Prepare releases. (#1640) * Prepare releases. * Re-export libp2p-request-response from libp2p crate. * Clean up changelogs. * Restore upper bounds. * Version 0.21 for the root crate. * Stricter lower bound in libp2p-websocket version in root crate. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> * Update release date. * Update misc/peer-id-generator/Cargo.toml Co-authored-by: Toralf Wittner <tw@dtex.org> Co-authored-by: Toralf Wittner <tw@dtex.org>
2020-07-01 15:36:20 +02:00
- Initial release.
Reference in New Issue Copy Permalink