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
RPC #466
Comments
1 |
2
should return an error when no/wrong parameter(s) are passed like a number instead of HEX etc. {"error":{"code":-32602,"message":"INVALID_PARAMS: Invalid method parameters (invalid name and/or type)"},"id":2,"jsonrpc":"2.0"} message can differ, but the code should stay the same |
3
should return error code Please return an error as follows: {"error":{"code":-32602,"message":"INVALID_PARAMS: Invalid method parameters (invalid name and/or type)"},"id":2,"jsonrpc":"2.0"} |
4
returns number not HEX |
5 |
6 |
With the exception of item 1, I think most of these issues have been addressed. @frozeman This situation occurs when the accounts have not been initialised. Can we write the tests to WARN when accounts array is empty and coinbase is nil/zero? We should be able to handle these situations without being explicit errors |
Re-open if there any pending issues left with the RPC |
NetStore Get retry
* initial * measure * initial test * block size debug * current progress * debug * progress * debug * it works * todo * linters * clean up * check for nonce gaps * clean up * cr * cr * cr * check tx pool on an error * stats * params * introduce config * min-max accounts * debug * debug * update * debug * skip
* fix: update worker nextL1MsgIndex for strange errors * more tests * bump version * refactor: add more context to tracing failure (ethereum#466) * bump version * bump version
In this thread i will add a comment per bug, as this are mostly minor issues.
The text was updated successfully, but these errors were encountered: