fluencelabs/rust-libp2p
1
0
Fork 0
mirror of https://github.com/fluencelabs/rust-libp2p synced 2025-05-29 10:41:21 +00:00
Code Issues Projects Releases Wiki Activity
rust-libp2p/misc/multistream-select/CHANGELOG.md

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

90 lines
2.8 KiB
Markdown
Raw Normal View History

.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
# 0.12.1 [Unreleased]
- Update `rust-version` to reflect the actual MSRV: 1.60.0. See [PR 3090].
[PR 3090]: https://github.com/libp2p/rust-libp2p/pull/3090
*: Prepare v0.49.0 (#2931)
2022-10-14 15:30:16 +01:00
# 0.12.0
misc/multistream-select/: Remove parallel dialing optimization (#2934) This is to avoid the usage of the now optional `ls` command, and stay compatible with go-multistream. Closes #2925
2022-09-29 15:36:11 +02:00
- Remove parallel dialing optimization, to avoid requiring the use of the `ls` command. See [PR 2934].
[PR 2934]: https://github.com/libp2p/rust-libp2p/pull/2934
*: Prepare v0.42.0 (#2440)
2022-01-27 11:29:09 +01:00
# 0.11.0 [2022-01-27]
*: 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
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.10.4 [2021-11-01]
*/: Replace `Into` with `From` (#2169) Unless restricted by orphan rules, implementing `From` is superior because it implies `Into` but leaves the choice to the user, which one to use. Especially for errors, `From` is convenient because that is what `?` builds on. Co-authored-by: Max Inden <mail@max-inden.de>
2021-08-03 23:55:36 +10:00
- Implement `From<io::Error> for ProtocolError` instead of `Into`.
[PR 2169](https://github.com/libp2p/rust-libp2p/pull/2169)
*: Prepare v0.36.0 release
2021-03-17 15:28:13 +01:00
# 0.10.3 [2021-03-17]
*: 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 multistream-select-0.10.2
2021-03-01 15:56:00 +01:00
# 0.10.2 [2021-03-01]
- Re-enable "parallel negotiation" if the dialer has 3 or more
alternative protocols.
[PR 1934](https://github.com/libp2p/rust-libp2p/pull/1934)
Prepare v0.35 (#1957)
2021-02-15 20:06:50 +01:00
# 0.10.1 [2021-02-15]
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.10.0 [2021-01-12]
*: 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.
Prepare multistream-select-0.9.1
2020-12-02 16:41:59 +01:00
# 0.9.1 [2020-12-02]
- Ensure uniform outcomes for failed negotiations with both
`V1` and `V1Lazy`.
[PR 1871](https://github.com/libp2p/rust-libp2p/pull/1871)
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.9.0 [2020-11-25]
[multistream-select] Fix `ls` response encoding/decoding (spec-compliance). (#1811) * Fix ls response encoding/decoding. Thereby remove the now unnecessary arbitrary protocol name length limit. Since it an 'ls' response is always terminated with a dedicated newline (and thus ends with two newlines), an 'ls' response with a single protocol can be disambiguated from a single protocol response by this additional newline. * More commentary * Update versions and changelogs. * Resolve remaining conflict. * Permit empty ls responses, as before.
2020-11-18 12:03:07 +01:00
[multistream] Make the lazy variant more interoperable. (#1855) * Make the lazy variant interoperable. The remaining optimisation for `V1Lazy` for a listener in the negotiation, whereby the listener delays flushing of the multistream version header, is hereby removed. The remaining effect of `V1Lazy` is only on the side of the dialer, which delays flushing of its singular protocol proposal in order to send it together with the first application data (or an attempt is made to read from the negotiated stream, which similarly triggers a flush of the protocol proposal). This permits `V1Lazy` dialers to be interoperable with `V1` listeners. The remaining theoretical pitfall whereby application data gets misinterpreted as another protocol proposal by a listener remains, however unlikely. `V1` remains the default, but we may eventually risk just making this lazy dialer flush a part of the default `V1` implementation, removing the dedicated `V1Lazy` version identifier. * Update CHANGELOG * Separate versions from mere header lines. Every multistream-select version maps to a specific header line, but there may be different variants of the same multistream-select version using the same header line, i.e. the same wire protocol. * Cleanup * Update misc/multistream-select/CHANGELOG.md
2020-11-25 10:21:02 +01:00
- Make the `V1Lazy` upgrade strategy more interoperable with `V1`. Specifically,
the listener now behaves identically with `V1` and `V1Lazy`. Furthermore, the
multistream-select protocol header is now also identical, making `V1` and `V1Lazy`
indistinguishable on the wire. The remaining central effect of `V1Lazy` is that the dialer,
if it only supports a single protocol in a negotiation, optimistically settles on that
protocol without immediately flushing the negotiation data (i.e. protocol proposal)
and without waiting for the corresponding confirmation before it is able to start
sending application data, expecting the used protocol to be confirmed with
the response.
[multistream-select] Fix `ls` response encoding/decoding (spec-compliance). (#1811) * Fix ls response encoding/decoding. Thereby remove the now unnecessary arbitrary protocol name length limit. Since it an 'ls' response is always terminated with a dedicated newline (and thus ends with two newlines), an 'ls' response with a single protocol can be disambiguated from a single protocol response by this additional newline. * More commentary * Update versions and changelogs. * Resolve remaining conflict. * Permit empty ls responses, as before.
2020-11-18 12:03:07 +01:00
- Fix the encoding and decoding of `ls` responses to
be spec-compliant and interoperable with other implementations.
For a clean upgrade, `0.8.4` must already be deployed.
*: 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.8.5 [2020-11-09]
misc/multistream-select: Interpretation of EOF as Failed negotiation (#1823) Treat EOF error as [`NegotiationError::Failed`], not as [`NegotiationError::ProtocolError`], allowing dropping or closing an I/O stream as a permissible way to "gracefully" fail a negotiation. This is e.g. important when a listener rejects a protocol with [`Message::NotAvailable`] and the dialer does not have alternative protocols to propose. Then the dialer will stop the negotiation and drop the corresponding stream. As a listener this EOF should be interpreted as a failed negotiation.
2020-11-09 16:04:00 +01:00
- During negotiation do not interpret EOF error as an IO error, but instead as a
negotiation error. See https://github.com/libp2p/rust-libp2p/pull/1823.
[multistream-select] Temporarily disable "parallel" negotiation. (#1807) * [multistream-select] Temp. disable "parallel" negotiation. In order to later change the "ls" responses for spec-compliance. * Update version. * Update misc/multistream-select/CHANGELOG.md Co-authored-by: Max Inden <mail@max-inden.de> Co-authored-by: Max Inden <mail@max-inden.de>
2020-10-20 15:11:20 +02:00
# 0.8.4 [2020-10-20]
- Temporarily disable the internal selection of "parallel" protocol
negotiation for the dialer to later change the response format of the "ls"
message for spec compliance. See https://github.com/libp2p/rust-libp2p/issues/1795.
Prepare release. (#1797)
2020-10-16 20:36:47 +02:00
# 0.8.3 [2020-10-16]
Update unsigned-varint requirement from 0.4 to 0.5 (#1761) * Update unsigned-varint requirement from 0.4 to 0.5 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/commits/v0.5.1) 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-16 10:27:33 +02:00
[multistream-select] Fix panic with `V1Lazy` (regression) and more convenient transport boxing. (#1783) * [multistream-select] Fix panic with V1Lazy and add integration tests. Fixes a panic when using the `V1Lazy` negotiation protocol, a regression introduced in https://github.com/libp2p/rust-libp2p/pull/1484. Thereby adds integration tests for a transport upgrade with both `V1` and `V1Lazy` to the `multistream-select` crate to prevent future regressions. * Cleanup. * Update changelog.
2020-10-07 11:10:54 +02:00
- Fix a regression resulting in a panic with the `V1Lazy` protocol.
[PR 1783](https://github.com/libp2p/rust-libp2p/pull/1783).
[multistream-select] Require remaining negotiation data to be flushed. (#1781) * Require remaining negotiation data to be flushed. There appears to still be an edge-case whereby the `remaining` data to send w.r.t. protocol negotiation to send is successfully written before a `poll_read` on a `Negotiated` stream, but where the subsequent `poll_flush()` is pending. Now `remaining` is empty and the next `poll_read()` will go straight to reading from the underlying I/O stream, despite the flush not having happened yet, which can lead to a form of deadlock during protocol negotiation. Rather than complicating the existing code further in order to accommodate for this case, it seems preferable to simplify the code by giving up on this optimisation that only affects the last negotiation protocol message sent by the "listener". So we give up on the ability to combine data sent by the "listener" immediately after protocol negotiation together with the final negotiation frame in the same transport-level frame/packet. * Update changelog. * Add missing comma.
2020-10-01 12:29:51 +02:00
- Fix a potential deadlock during protocol negotiation due
to a missing flush, potentially resulting in sporadic protocol
upgrade timeouts.
[PR 1781](https://github.com/libp2p/rust-libp2p/pull/1781).
Update unsigned-varint requirement from 0.4 to 0.5 (#1761) * Update unsigned-varint requirement from 0.4 to 0.5 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/commits/v0.5.1) 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-16 10:27:33 +02:00
- Update dependencies.
Prepare release. (#1620)
2020-06-22 11:41:28 +02:00
# 0.8.2 [2020-06-22]
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
- Updated dependencies.
Reference in New Issue Copy Permalink