GitLab

Or, really, just avoid accessing it. We don't need it.

This caused a concurrent map access panic under load.

* feat: total wants gauge

* fix: in gauges count wants regardless of which peers they're sent to

* fix: want block gauge calculation

* refactor: simplify peermanagerwants

Instead of tracking offsets, just create a "new" slice starting with the
broadcast cancel slice. Under the covers, this will just use the same memory
over and over.

* feat: small optimizations

* feat: move broadcast wantlist into the peermanager

This deduplicates some state and allows us to do less book-keeping for broadcast
wants. We should probably rename the PeerManager to the WantManager and rename the
WantManager to something else.

* fix: lint warnings

* refactor: add reverse index to peerWantManager to speed up cancels

* refactor: in peerWantManager use ForEach instead of allocating lists

This makes it easier to tell where module boundaries are.

And expose a separate function for _just_ getting want-blocks. When the user
runs `ipfs bitswap wantlist`, they expect to see everything the node is
currently looking for.
Co-Authored-By: dirkmc <dirkmdev@gmail.com>

This makes reading the docs much easier as it's clear what's "private" and
what's not.

fixes #238