-
-
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 on bad path via API #4461
Comments
The problem here is that an error occurs and we can't encode that error using protobuf. When the error occurs we call Digging through this made me wonder what happened before go-ipfs-cmds. Here is the output for 0.4.13:
|
Branch with more informative error: https://github.com/ipfs/go-ipfs-cmds/tree/fix/cant-encode-error |
Oh. THIS bug. #2517 |
I'm seeing the following error (produced by the daemon) when manually calling the API with a bad path (and asking for a protobuf output):
related to #2468
This is not fixed by ipfs/go-ipfs-cmds#34
The text was updated successfully, but these errors were encountered: