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
Since those String are user-defined, this error could easily occurs. This prevents me from parsing the whole message, and therefor see other attributes. I'm not sure what's the best solution here.
One way could be having Vec<u8> instead of String for user-defined attributes instead, and then suggest to convert that to UTF8 if needs to be? Having two structs, one with String and one with Vec<u8> feels overkill.
The text was updated successfully, but these errors were encountered:
If you look at https://testnet-explorer.publicawesome.dev/stargaze/tx/F31D90E03B1F9020A5B99D726E82B65BB24CE938CC99DDD0B40DA28BA9B178A9 the
description
field is malformed UTF8 and trying to decode it gets me afailed to decode Protobuf message: SudoContractProposal.description: invalid string value: data is not UTF-8 encoded
The protobuf type is defined at:
cosmos-rust/cosmos-sdk-proto/src/prost/wasmd/cosmwasm.wasm.v1.rs
Line 511 in df40384
with
description
as aString
.Since those
String
are user-defined, this error could easily occurs. This prevents me from parsing the whole message, and therefor see other attributes. I'm not sure what's the best solution here.One way could be having
Vec<u8>
instead ofString
for user-defined attributes instead, and then suggest to convert that to UTF8 if needs to be? Having two structs, one withString
and one withVec<u8>
feels overkill.The text was updated successfully, but these errors were encountered: