-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Insufficient broadcast txs error info returned by POST /txs #4858
Comments
Can you summarize the issue/problem you're experiencing @whunmr? I'm having trouble understanding. Also note, |
Thanks for the reply. we need the POST /txs api to return block hash and other info, when runtx failes. |
have rephrased the problem summary in first comment. hope it's more clearer. Also thanks for the notice |
In functional tests sure, but this does not reflect a common live network situation. But I see what you mean. The solution is to not return an error:
|
Summary of Bug
Not consistent return value structure between success and failure result of POST /txs API.
when execution of tx failed with some error (e.g.: delegate without enough funds)
the POST /txs API will return like:
the problem is when we got this error result, can not know the txhash for further use
Version
Steps to Reproduce
codes
broadcast.go:47
rest.WriteErrorResponse
.For Admin Use
The text was updated successfully, but these errors were encountered: