You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sequencer reports that a bridge lock action failed even though it was checking a bridge unlock action.
The error message should be fixed. To not let this happen in the future: 1. Can the boiler plate also be replaced by a macro? And 2: can we make use of astria_core::Protobuf::full_name() to print the name of the failed action?
SuperFluffy
changed the title
Duplicate error messages for two different actions is confusing
Sequencer reports the wrong action as having failed
Sep 6, 2024
…#1505)
## Summary
The error message for stateless checks on `BridgeUnlock` actions
incorrectly states `BridgeLock` as the failing error.
## Changes
- change the error message that wraps the stateless check for
`BridgeUnlock` actions
## Related Issues
Link any issues that are related, prefer full github links.
closes#1465
…#1505)
The error message for stateless checks on `BridgeUnlock` actions
incorrectly states `BridgeLock` as the failing error.
- change the error message that wraps the stateless check for
`BridgeUnlock` actions
Link any issues that are related, prefer full github links.
closes#1465
…#1505)
The error message for stateless checks on `BridgeUnlock` actions
incorrectly states `BridgeLock` as the failing error.
- change the error message that wraps the stateless check for
`BridgeUnlock` actions
Link any issues that are related, prefer full github links.
closes#1465
Sequencer reports that a bridge lock action failed even though it was checking a bridge unlock action.
The error message should be fixed. To not let this happen in the future: 1. Can the boiler plate also be replaced by a macro? And 2: can we make use of
astria_core::Protobuf::full_name()
to print the name of the failed action?astria/crates/astria-sequencer/src/transaction/mod.rs
Lines 130 to 137 in f46d7f5
┆Issue Number: ENG-800
The text was updated successfully, but these errors were encountered: