-
Notifications
You must be signed in to change notification settings - Fork 226
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.
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
Deserialization of tendermint::block::Header
type fails unexpectedly
#1309
Comments
Just to be clear, you're using tendermint-rs v0.27.0, right? If so, have you tried the latest release of tendermint-rs? (v0.31.1) Asking because we don't have capacity to support older releases of tendermint-rs at present. |
Makes sense. I just tested with |
@thanethomson It looks like #[test]
fn test_tm_block_id_serde_roundtrip() {
let header: tendermint::block::Header = serde_json::from_str(HEADER_JSON).unwrap();
let last_block_id: tendermint::block::Id = header.last_block_id.unwrap();
let serialized = postcard::to_stdvec(&last_block_id).unwrap();
let _deserialized: tendermint::block::Id = postcard::from_bytes(&serialized).unwrap();
} |
Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies.
Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies.
Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies.
I think the serde trait impls on all of those types are designed for serializing/deserializing JSON, not arbitrary other formats. Protobufs are the preferred binary encoding. |
Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies. Feature gate `CelestiaService` and its netowkr/io dependencies behind the "native" feature, re-organizing files as necessary.
Yeah, that seems to be the case. I know that serialization in this package has always been a bit tricky due to compatibility requirements. Just documenting the restriction is probably sufficient for now. |
* Make compatible with risc0. Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies. Feature gate `CelestiaService` and its netowkr/io dependencies behind the "native" feature, re-organizing files as necessary. * Update to latest sdk. Add CI * Remove outdated da_app files
Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies. Feature gate `CelestiaService` and its netowkr/io dependencies behind the "native" feature, re-organizing files as necessary.
…19) * Make compatible with risc0. Introduce the CompactHeader type, which allows us to circumvent informalsystems/tendermint-rs#1309. Update to Tendermint 0.32, which allows removal of unnecessary data copies. Feature gate `CelestiaService` and its netowkr/io dependencies behind the "native" feature, re-organizing files as necessary. * Update to latest sdk. Add CI * Update for latest sdk * Update to user prover-demo branch of sdk * Bump commit version for sdk * Update to latest sdk * Fix after Encode/Decode removals (#18) * Clippy fixes * Add header_respons.json * Remove unneeded patch --------- Co-authored-by: Nikolai Golub <nikolai@sovlabs.io>
Will try to put up a PR to fix the documentation and close this issue later. @thanethomson @romac, any thoughts on where the most appropriate place for that documentation would be? As an aside, it seems like it should be relatively straightforward to use the |
@preston-evans98 but why not use Protobuf as a binary serialization? It's the canonical binary format for these types |
@tarcieri TBC my use case is currently workable without serde, so I'm fine with just documenting the lack of support and closing out the issue. That being said, there are a few reasons why someone might want to use serde over protobuf. Performance is one - a format like Another reason is library support. Lots and lots of packages are compatible with serde and have blanket implementations for their traits in terms of serde. (In fact, that's what prompted this issue - i wanted to use a library and it had default support for serde - so I just used it. But because of the bug, data was getting silently garbled in-flight - so I had to hand write some logic use protobufs instead). The final reason is just familiarity. Pretty much every Rust programmer has used the Serde APIs, and IME prost is a lot less widely know. |
A proliferation of binary formats harms interoperability. It already exists with Amino and Protobuf |
What went wrong?
An attempt to serialize and then deserialize a
tendermint::block::Header
using a binary data format (postcard
) returned an error:Err(DeserializeBadOption)
.This error is not a bug in
postcard
- in my testing also occurs when attempting roundtrip serialization with other binary data formats.Steps to reproduce
Attempt roundtrip serialization of a
tendermint::block::Header
with a suitable (non-JSON) data format. The following test case usestendermint = "0.27"
and,serde_json = "1"
, andpostcard = { version = "1", features = ["use-std"]}
.The provided test will fail with the following output:
Definition of "done"
Either roundtrip serialization succeeds using binary data formats, or documentation is added explaining that serialization to/from formats other than json is not supported.
The text was updated successfully, but these errors were encountered: