Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Script to simplifiy gathering debug stats #6457

Closed
magik6k opened this issue Jun 19, 2019 · 6 comments
Closed

Script to simplifiy gathering debug stats #6457

magik6k opened this issue Jun 19, 2019 · 6 comments
Labels
exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue topic/tools Topic tools

Comments

@magik6k
Copy link
Member

magik6k commented Jun 19, 2019

Currently gathering debug info involves running some commands manually, and putting the files somewhere. We should have a script to automate that (bonus point for a tiny pastebin like service for those)

@magik6k magik6k added help wanted Seeking public contribution on this issue topic/tools Topic tools exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors labels Jun 19, 2019
@Tajallah
Copy link

Tajallah commented Jul 5, 2019

Hello, I'm new and I'd like to get started contributing to this project. I've never collaborated on github before and would like to work on this. How do I get started?

@Stebalien
Copy link
Member

If you haven't already, read https://guides.github.com/introduction/flow/. Once you have, this script this issue is talking about needs to:

  1. Run all the commands from https://github.com/ipfs/go-ipfs/blob/master/docs/debug-guide.md#beginning.
  2. Compile the output files (along with a copy of the IPFS binary) into a single archive (e.g., using tar).

@Kubuxu
Copy link
Member

Kubuxu commented Jul 6, 2019

@Tajallah
Copy link

Tajallah commented Jul 6, 2019

Oh, it looks like that's already done then.

@Kubuxu
Copy link
Member

Kubuxu commented Jul 7, 2019

Yeah, we just should mention it in our docs.

@Stebalien
Copy link
Member

Given that this was just a documentation issue, I've filed a fix in #6486.

lanzafame pushed a commit that referenced this issue Jul 30, 2019
ralendor pushed a commit to ralendor/go-ipfs that referenced this issue Jun 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
exp/novice Someone with a little familiarity can pick up good first issue Good issue for new contributors help wanted Seeking public contribution on this issue topic/tools Topic tools
Projects
None yet
Development

No branches or pull requests

4 participants