-
Notifications
You must be signed in to change notification settings - Fork 787
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Fix error with work_cancel
RPC request
#2916
Conversation
@koczadly did you mean work_cancel ? Thanks for the fix, we require however that commits are GPG-signed. If you don't mind we can alternatively commit the patch ourselves with you as co-author. |
…successfully, and implement nano::error_rpc::empty_response error code to catch future errors.
Yeah sorry, I meant work_cancel. I've squashed and re-committed it with a signature, apologies. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just some minor suggestions
work_cancel
currently returns no response data when successful, which results in an "Empty response" error being returned. Appears to have been broken from PR #1032.This PR adds:
{"success": ""}
as the response forwork_cancel
nano::error_rpc::empty_response
error code, which is returned for empty responses (previously only an error string was passed, but without an error code).Unfortunately I've been unable to test this as I couldn't get boost to link up with VS correctly. Not sure what I'm doing wrong, so you'll have to rely on the CI results.