-
Notifications
You must be signed in to change notification settings - Fork 18
Conversation
The given timeout will be decremented 2s at every network hop, | ||
ensuring peers try to return their diagnostics before the initiator's | ||
timeout. If the timeout is too small, some peers may not be reached. | ||
30s and 60s are reasonable timeout values, though network vary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"though network vary" sounds wrong
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@whyrusleeping Need your feedback on this. These need to be changed. |
Note: 0.4.0 has an extra subcommand to ipfs diag
|
@RichardLitt Timeout is global: find the relevant go-code and put it in a thing. |
Added subcmds. Also edited them, so, this PR should be merged first. ipfs/kubo#2487 |
4325e00
to
3adbdfe
Compare
Final thing to do: Add a PR for timeout. However, the rest of this is RFCR and then RFM. |
Mentioned PR in ipfs/kubo#2583. Merging this as that isn't relevant to the direct code in this PR. |
43c56a4
to
0e92ddf
Compare
No description provided.