This repository has been archived by the owner on Feb 1, 2023. It is now read-only.
Simulate DONT_HAVE when peer doesn't respond to want-block (new peers) #284
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
16 tasks
dirkmc
changed the title
Closed
Stebalien
approved these changes
Mar 10, 2020
|
Verification that this branch performs better than the old bitswap:
|
Jorropo
pushed a commit
to Jorropo/go-libipfs
that referenced
this pull request
Jan 26, 2023
…eers Simulate DONT_HAVE when peer doesn't respond to want-block (new peers) This commit was moved from ipfs/go-bitswap@3a82e57
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We should simulate a DONT_HAVE response when we send want-block to a peer and the peer doesn't respond within a reasonable amount of time.
We have this already for older peers (that don't support DONT_HAVE).
This PR adds support for newer peers (that do support DONT_HAVE).