GitLab

fixes a CPU issue when canceling find provider requests

Bumps [go.uber.org/zap](https://github.com/uber-go/zap) from 1.14.1 to 1.15.0.
- [Release notes](https://github.com/uber-go/zap/releases)
- [Changelog](https://github.com/uber-go/zap/blob/master/CHANGELOG.md)
- [Commits](https://github.com/uber-go/zap/compare/v1.14.1...v1.15.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Removes any and all requirements on CGO. Previously, ipfs would fail to build if
CGO wasn't explicitly disabled and no C compiler was available.

fixes #7015

1. Update go-ipfs-config to fix default datastore.
2. Update TOC.
3. Update profiles list and indicate that badger isn't experimental.

Don't abort in Accept when a single relay connection aborts.

fixes #7206

* Don't forget observed addresses from connected peers.
* Avoid many possible identify protocol races.
* Fix some dht events.

Ensure we send cancels when closing the session.

fixes a small bug in query notifications that was causing a test to fail

1. Increase broadcast timeout.
2. Fix use of sessions when pinning.

This also includes some bitswap changes to reduce some memory allocations and
optimize some hot spots.

More performance improvements.

Specifically:

1. Don't add peers with IPv6 addresses outside the 2000::/3 range to the WAN
DHT. These peers are not on the public internet.
2. Do add these peers to the LAN DHT. Really, that's the "catch all other" DHT.

Another attempt to fix #7115.

Reduces allocations

1. Enable AutoNATService on _all_ nodes by default. If it's an issue, we can
disable it in RC3 but this will give us the best testing results.
2. Expose options to configure AutoNAT rate limiting.

Remove some allocation hotspots

Hopefully fixes the message queue bloat issue.

And remove retry logic. This was flatfs specific and we've moved the logic down
into flatfs itself.

This update:

* Retries in more cases when we run out of file descriptors.
* Ensures we don't leak temporary files on batch put.

fixes #7115

And only join the WAN DHT if we're publicly reachable.

* QUIC: update to a new protocol version
* DHT: add some extra checks

This still works over "loosely defined" .car files
Please refer to the sharness tests for extra info

We can tighten this up if the sentiment is "Postel was wrong"

fixes https://github.com/ipfs/go-ipfs/issues/6986

This upgrades to the next DHT version, but in backwards compatibility mode.

This commit upgrades go-ipfs-cmds and configures the commands HTTP API Handler
to only allow POST/OPTIONS, disallowing GET and others in the handling of
command requests in the IPFS HTTP API (where before every type of request
method was handled, with GET/POST/PUT/PATCH being equivalent).

The Read-Only commands that the HTTP API attaches to the gateway endpoint will
additional handled GET as they did before (but stop handling PUT,DELETEs).

By limiting the request types we address the possibility that a website
accessed by a browser abuses the IPFS API by issuing GET requests to it which
have no Origin or Referrer set, and are thus bypass CORS and CSRF protections.

This is a breaking change for clients that relay on GET requests against the
HTTP endpoint (usually :5001). Applications integrating on top of the
gateway-read-only API should still work (including cross-domain access).
Co-Authored-By: Steven Allen <steven@stebalien.com>
Co-Authored-By: Marcin Rataj <lidel@lidel.org>

Prepare for an RC. This also re-re-disables stream write coalescing till we get
a chance to thoroughly profile it.