-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
sending SIGINT to ipfs repo verify
incorrectly reports verify complete when daemon isn't running
#4360
Comments
I look into it. |
With master I am now getting:
@keks can you have a look at this, this is likely related to the command code |
@keks I just tried this on master, without the daemon running here is the result:
So not getting With the daemon running I get |
Phew, this one is tricky. I think the issue is that the program terminates too quickly to set the exit code after the cancel is received. |
The error is thrown here and we can't pass it on from there on. Thinking through the options. |
> curl -i "http://localhost:5001/api/v0/object/get?arg=&encoding=protobuf"
related to #2468 |
Version information:
go-ipfs version: 0.4.12-rc1-
Repo version: 6
System version: amd64/windows
Golang version: go1.9
Type:
Bug
Severity:
Medium
Description:
Sending a SIGINT using CTRL+C to
ipfs repo verify
without the daemon running causes the command to reporteven though the command did not get a chance to complete. Before it reports this message, it appears to keep processing blocks for a few seconds until it finally stops.
When the daemon is running, canceling the
ipfs repo verify
command instead spits out an error. I'm not sure if this is desirable, but at least it doesn't report that the verify is complete.Perhaps the output in both cases (daemon running and stopped) should report something like
The text was updated successfully, but these errors were encountered: