search

berty / go-orbit-db

Go version of P2P Database on IPFS
https://berty.tech
Apache License 2.0
422 stars 57 forks source link

chore(deps): bump github.com/libp2p/go-libp2p from 0.26.4 to 0.27.8 #138

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/libp2p/go-libp2p from 0.26.4 to 0.27.8.

Release notes

Sourced from github.com/libp2p/go-libp2p's releases.

v0.27.8

This patch release contains backports of:

Note that in order to be protected against the DoS attack making use of large RSA keys, it's necessary to update to this patch release AND to use the updated Go compiler (1.20.7 or 1.19.12, respectively).

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.27.7...v0.27.8

v0.27.7

What's Changed

  • fix: in the swarm move Connectedness emit after releasing conns #2373
  • identify: set stream deadlines for Identify and Identify Push streams #2382

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.27.6...v0.27.7

v0.27.6

What's Changed

  • Clean up stream scope in case of error

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.27.5...v0.27.6

v0.27.5

What's Changed

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.27.3...v0.27.5

v0.27.4

What's Changed

  • identify
    • Fixed an issue where we now avoid spuriously triggering pushes
    • Fixed an issue where signed peer records weren’t rejected if the signature didn’t match
  • swarm
    • Fixed duplicate tracking in dial worker loop

v0.27.3

This patch release contains a fix for a rare panic that occurs on Windows systems (backport of libp2p/go-libp2p#2276).

Full Changelog: https://github.com/libp2p/go-libp2p/compare/v0.27.1...v0.27.3

v0.27.2

What's Changed

quic: fix race condition when generating random holepunch packet (libp2p/go-libp2p#2263) webtransport: initialize the certmanager when creating the transport (libp2p/go-libp2p#2268)

... (truncated)

Changelog

Sourced from github.com/libp2p/go-libp2p's changelog.

Table Of Contents

v0.28.0

🔦 Highlights

Smart Dialing

This release introduces smart dialing logic. Currently, libp2p dials all addresses of a remote peer in parallel, and aborts all outstanding dials as soon as the first one succeeds. Dialing many addresses in parallel creates a lot of churn on the client side, and unnecessary load on the network and on the server side, and is heavily discouraged by the networking community (see RFC 8305 for example).

When connecting to a peer we first determine the order to dial its addresses. This ranking logic considers a number of corner cases described in detail in the documentation of the swarm package (swarm.DefaultDialRanker). At a high level, this is what happens:

  • If a peer offers a WebTransport and a QUIC address (on the same IP:port), the QUIC address is preferred.
  • If a peer has a QUIC and a TCP address, the QUIC address is dialed first. Only if the connection attempt doesn't succeed within 250ms, a TCP connection is started.

Our measurements on the IPFS network show that for >90% of established libp2p connections, the first connection attempt succeeds, leading a dramatic decrease in the number of aborted connection attempts.

We also added new metrics to the swarm Grafana dashboard, showing:

  • The number of connection attempts it took to establish a connection
  • The delay introduced by the ranking logic

This feature should be safe to enable for nodes running in data centers and for most nodes in home networks. However, there are some (mostly home and corporate networks) that block all UDP traffic. If enabled, the current implementation of the smart dialing logic will lead to a regression, since it preferes QUIC addresses over TCP addresses. Nodes would still be able to connect, but connection establishment of the TCP connection would be delayed by 250ms.

In a future release (see #1605 for details), we will introduce a feature called blackhole detection. By observing the outcome of QUIC connection attempts, we can determine if UDP traffic is blocked (namely, if all QUIC connection attempts fail), and stop dialing QUIC in this case altogether. Once this detection logic is in place, smart dialing will be enabled by default.

More Metrics!

Since the last release, we've added metrics for:

WebTransport

... (truncated)

Commits


Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/berty/go-orbit-db/network/alerts).

Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

codecov[bot] commented 1 year ago

Codecov Report

Patch coverage has no change and project coverage change: +0.07% :tada:

Comparison is base (368618e) 62.76% compared to head (5fc3ef9) 62.84%.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## master #138 +/- ## ========================================== + Coverage 62.76% 62.84% +0.07% ========================================== Files 37 37 Lines 2546 2546 ========================================== + Hits 1598 1600 +2 + Misses 649 647 -2 Partials 299 299 ``` | Flag | Coverage Δ | | |---|---|---| | unittests | `62.84% <ø> (+0.07%)` | :arrow_up: | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=berty#carryforward-flags-in-the-pull-request-comment) to find out more. [see 1 file with indirect coverage changes](https://app.codecov.io/gh/berty/go-orbit-db/pull/138/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=berty)

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

jefft0 commented 1 year ago

The dependabot PR on berty was a minor update from 0.27.6 to 0.27.8 . This is a major update from 0.26.4 to 0.27.8 which changes many other package versions in go.mod. We need to discuss if this is OK.

github-actions[bot] commented 7 months ago

:tada: This PR is included in version 1.22.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: