-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
panic has occurred in the commands handler #7912
Comments
As per the stack trace, if it's occurring in 0.6.0, it can occur in the latest version as well. I'm not sure why |
I think this was fixed by #7612 and is in v0.7.0+, but feel free to reopen if the issue still occurs. |
@aschmahmann I'm not sure what that commit does.
Here, err is from parent scope and would be nil. So, we are probably returning nil here. Do let me know if that isn't correct. It should have been |
yep, looks like it should've been returning |
Should we reopen this then? Or you can fix it in another PR, I'll leave it up to you. :) |
It's a different issue. The only bad thing that happens is that an error is swallowed during what is likely just a user aborting the command early. I'll just open a PR on it (and post back the PR # here as a reference) Update: PR opened at #7942 |
just got a panic with go-ipfs. Not yet running 0.7 - so feel free to close - but maybe the stacktrace is useful to you - so reporting it here.
Version information:
ipfs version --all
go-ipfs version: 0.6.0
Repo version: 10
System version: amd64/linux
Golang version: go1.14.4
Description:
The node was hanging and not serving http anymore. Needed to kill it with ^C
The text was updated successfully, but these errors were encountered: