-
Notifications
You must be signed in to change notification settings - Fork 52
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
No error check leads to chrash #8
Comments
Please find in the attachment the changes I've made locally.
|
Oups wrong method. It was sendTransaction that crashed, but the change is the same:
|
Now the client instead of crashing can retrieve error information and do something about it like so:
|
May I ask whether you intend to change classes derived from AbstractMethods to check for errors returned by ClientInterface? I see that three days ago Personal::unlockAccount was changed to check for errors, but IMHO that change didn’t go far enough. I think that to be useful in the real-world applications all functions should call getRpcErrorCode before calling getRpcResult. Also I think that error code and error message should be stored by the AbstractMethods alongside the $client variable to be retrieved by EthereumClient.
The text was updated successfully, but these errors were encountered: