basichost can remember invalid protocol preference
Open
Nobody has claimed this yet.
exp/expert
help wanted
kind/bug
status/ready
- Dominant language
- Go
- Stars
- 6.9k
- Forks
- 1.3k
- Avg merge
- 13d 21h
- Merged PRs (30d)
- 1
Description
If i connect node A to node B, and they speak bitswap 1.1.0, node B will remember that node A supports that protocol. if node A is then downgraded to only support bitswap 1.0.0, node B will still attempt to only communicate over bitswap 1.1.0, resulting in a failure to communicate.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Use the reported node A/node B connection and downgrade sequence as the reproduction, then inspect basichost's remembered protocol preference handling. Done means node B renegotiates with node A's currently supported bitswap 1.0.0 instead of attempting only bitswap 1.1.0, with regression coverage for this sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100