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
Currently, when converting an incoming IBC message of Any type to a MsgEnvelope, we are mapping decoding errors to a variant of RouterError (e.g. here), leading to confusion. Thus, this issue should aim to:
Fix incorrect mapping
Utilize more efficient manner to capture the source error
We came across this issue in #949 and it is currently blocked on #270. We can address this after refactoring our error handling system.
The text was updated successfully, but these errors were encountered:
Farhad-Shabani
changed the title
Improve Error handling when decoding Any to MsgEnvelope
Improve error handling when decoding Any to MsgEnvelopeNov 7, 2023
Problem Statement
Currently, when converting an incoming IBC message of
Any
type to aMsgEnvelope
, we are mapping decoding errors to a variant ofRouterError
(e.g. here), leading to confusion. Thus, this issue should aim to:We came across this issue in #949 and it is currently blocked on #270. We can address this after refactoring our error handling system.
The text was updated successfully, but these errors were encountered: