Skip to content
This repository has been archived by the owner on Apr 29, 2020. It is now read-only.

Added group diag #40

Merged
merged 5 commits into from
Apr 19, 2016
Merged

Added group diag #40

merged 5 commits into from
Apr 19, 2016

Conversation

RichardLitt
Copy link
Contributor

No description provided.

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.
Copy link
Collaborator

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RichardLitt
Copy link
Contributor Author

@whyrusleeping Need your feedback on this. These need to be changed.

@daviddias
Copy link
Contributor

Note: 0.4.0 has an extra subcommand to ipfs diag

ipfs diag cmds - List commands run on this ipfs node

@RichardLitt
Copy link
Contributor Author

@RichardLitt Timeout is global: find the relevant go-code and put it in a thing.

@RichardLitt
Copy link
Contributor Author

Added subcmds. Also edited them, so, this PR should be merged first. ipfs/kubo#2487

@RichardLitt
Copy link
Contributor Author

Final thing to do: Add a PR for timeout. However, the rest of this is RFCR and then RFM.

@RichardLitt RichardLitt removed their assignment Mar 22, 2016
@RichardLitt
Copy link
Contributor Author

Mentioned PR in ipfs/kubo#2583. Merging this as that isn't relevant to the direct code in this PR.

@RichardLitt RichardLitt merged commit 01e73a4 into master Apr 19, 2016
@RichardLitt RichardLitt deleted the feature/diag branch April 19, 2016 14:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants