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
It looks like there are some inconsistencies between the JSON serialization and deserialization of ConnectionEnd in ibc-rs. I tried to query for the connection end from sov-ibc, and when try to parse the response using QueryConnectionResponse, I got the error:
So it seems like the commitment_prefix field is serialized into string during serialization, but is expected to be wrapped inside a CommitmentPrefix wrapper field during JSON deserialization.
Note that the current manually derived Serialize instance for CommitmentPrefix is also incorrectly implemented. It uses the Debug instance of CommitmentPrefix, but the Debug implementation serializes a commitment prefix with invalid UTF-8 as "<not valid UTF8: {:?}>".
Feature Summary
Raised by @soareschen:
Proposal
Either auto-derive
serde::Serialize
as well forCommitmentPrefix
, or manually deserialize it so that parsing is consistent.The text was updated successfully, but these errors were encountered: