Steven Allen
Steven Allen
@Kubuxu Maybe. However I don't think we usually have >1000 issues opened per quarter (although I may be wrong).
We also need a way to keep track of issues needing responses.
- The entry point to this code is https://github.com/ipfs/go-bitswap/tree/master/internal/decision. - You'll probably need to modify the [`PeerCompare`](https://github.com/ipfs/go-peertaskqueue/blob/0d567453333974bb0639dbbaff5740f6d5718dc7/peertracker/peertracker.go#L72-L104) function to take some form of priority into account when deciding between peers....
It doesn't look like these names map to that table. Other issues: 1. "v0" is dag-pb with v0 CIDs (I think?) 2. cbor should be dag-cbor. We'll probably need to...
(bad github)
This is actually a more general issue. We should only remember "DONT_HAVEs" for a peer when those CIDs are in the peer's wantlist. This issue can also arise when we...
Actually, do we even need to record "don't have"s? IIRC, we don't _remove_ things from wantlists until we stop wanting the block.
> Is there another scenario in which we send a cancel to a peer? When we cancel a want for a block (without canceling the rest of the session). That...
Ah... could you file a bug for that as well?
The goal was to _also_ migrate multihash.