-
Notifications
You must be signed in to change notification settings - Fork 54
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
bug: group_manager crashes with unhandled exception #2204
Labels
bug
Something isn't working
Comments
@alrevuelta @rymnc Any thoughts on this? |
yeah our error handling/retrying policy is not great. agree for graceful shutdown in case the eth node stops responding |
Unsure if related: #1958
I would retry yeap. |
@rymnc are you able to pick up this issue? |
Hi, this can be closed by #2250 |
1 task
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
wakunode2 will crash in group_manager.nim if the RPC node fails to respond or timeouts
It should probably either fail gracefully, or rather retry a few times before failing
It seems the culprit is probably
getJsonLogs
(https://github.com/status-im/nim-web3/blob/428b931e7c4f1284b4272bc2c11fca2bd70991cd/web3.nim#L535) throwing without specifyingRaises
and thus us not handling the exception?Impact
critical
To reproduce
Run nwaku-compose and observe the error if your Ethereum RPC node fails or timeouts
Expected behavior
Fail gracefully or retry without failing
Screenshots/logs
If applicable, add screenshots or logs to help explain your problem.
nwaku version/commit hash
State the version of
nwaku
where you've encountered the bug or, if built off a specific commit, the relevant commit hash. You can check the version by running./wakunode2 --version
.docker.io/wakuorg/nwaku:v0.21.2-rc.0
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: