-
Notifications
You must be signed in to change notification settings - Fork 71
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
remote_endpoint: Transport endpoint is not connected exception #1418
Milestone
Comments
Same error crashed another 3.2.4 node today. This node is not running state history, but is one of our transaction api nodes.
|
Fixed in 4.0: #1175 |
Added LGTM tag, and targeting this to merge into the 3.2 branch. Will put out a new release with the fix. |
heifner
added a commit
that referenced
this issue
Jul 26, 2023
heifner
added a commit
that referenced
this issue
Jul 26, 2023
[3.2] Ignore http error on remote_endpoint() causing terminate
heifner
added a commit
that referenced
this issue
Jul 26, 2023
heifner
added a commit
that referenced
this issue
Jul 26, 2023
[3.2 -> 4.0] Ignore http error on remote_endpoint() causing terminate
heifner
added a commit
that referenced
this issue
Jul 26, 2023
heifner
added a commit
that referenced
this issue
Jul 27, 2023
[4.0 -> main] Ignore http error on remote_endpoint() causing terminate
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version: 3.2.4
I know this is for wax. but the code should be the same. Nodeos throws an exception in the SHiP plugin. I think this type of errors should be recoverable. but the exception is never caught and stops the node.
Link to the reported line: https://github.com/AntelopeIO/leap/blob/v3.2.4/plugins/state_history_plugin/state_history_plugin.cpp#L376
Same but for wax-leap: https://github.com/cc32d9/wax-leap/blob/v3.2.4wax01/plugins/state_history_plugin/state_history_plugin.cpp#L376
The text was updated successfully, but these errors were encountered: