GitLab

Co-Authored-By: Peter Rabbitson <ribasushi@protocol.ai>

fix: non-blocking peerlog logging

Avoid ever blocking new connections in the peer logger. Instead:

1. Send all new peers to a highly buffered channel.
2. Emit "dropped event" errors whenever we detect that we're dropping events and falling behind.
3. Don't log protocols, they're too large.
4. Don't log disconnects, we don't need them.

chore: update go-ipfs-provider

doc: update go-ipfs docs for 0.5.0 release

fixes #7015

update go-libp2p-quic-transport to v0.3.5

Mostly:

1. Remove old experiments.
2. Update reasons for features being experimental.
3. Comment on experiments that will be enabled in the near future.

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

Add additional documentation links to the new issue screen

Update issue templates

* Remove question template: links to help have been added
* Add need/triage labels
* Do not ask users to open issues in ipfs/ipfs (issues heavily discouraged there).

docs: note that ShardingEnabled is a global flag

People may assume that HAMT gets enabled only for directories over some arbitrary threshold.
This is not the case. Right now it is a global setting 
which will impact the final CID of all directories produced by ipfs.add.

chore: update circuit relay

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

fix: don't hang on bootstrap

fixes #7206

release: 0.5.0-rc4

chore: update deps

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

update log helptext to match actual levels

Chore/harden car test a bit harder

chore: update bitswap

Ensure we send cancels when closing the session.