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.

Sign up for GitHub

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

Jump to bottom

[bug] relayer messages are loaded with the wrong operation_status from db #5301

Open

daniel-savu opened this issue Jan 27, 2025 · 0 comments

Labels

bug monitoring relayer reliability

Contributor

daniel-savu commented Jan 27, 2025

some things @tkporter and I noticed:

message failed to be submitted here due to nonce too low: https://cloudlogging.app.goo.gl/JWxJSBgoreoisx7P9
then message failed when estimated in the prepare step: https://cloudlogging.app.goo.gl/vHDANesCFoizyrz39
right before the restart at 11:39, in the last Popped OpQueue operations log, the message had an "Error estimating gas" status
however right after startup, the message had am "Error submitting" status.

We thought persisted statuses are currently not loaded at all on restart but this contradicts that (soon to be fixed by feat: attempt to fetch operation status in database upon relayer restart #5182)
this suggests the persisted status was wrong, as the "Error estimating gas" error is the one that should've been loaded from the db at startup

daniel-savu added bug monitoring relayer reliability labels

daniel-savu added this to Hyperlane Tasks

daniel-savu moved this to Backlog in Hyperlane Tasks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment