-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ibc-types: bump prost, tendermint, ibc-proto, ics23 (#94)
Updates the following dependencies: + ibc-proto: 0.42.2 -> 0.51.1 + ics23: 0.11.3 -> 0.12.0 + prost: 0.12.0 -> 0.13.3 + tendermint: 0.34.0 -> 0.40.0 + tendermint-light-client-verifier: 0.34.0 -> 0.40.0 + tendermint-proto: 0.34.0 -> 0.40.0 + tendermint-rpc: 0.34.0 -> 0.40.0 + tendermint-testgen: 0.34.0 -> 0.40.0 The bump to the latest tendermint version required bumping prost, which in turns required updates of ibc-proto and ics23 (where I opted for their latest releases, respectively). The two larger changes are: 1. From [email protected] onward conversions between `core::time::Duration` and `protobuf.google.Duration` are now fallible. I introduced a newtype wrapper `CometBftDuration` to restore the previous behavior saturating at `i64::MAX` (for seconds) and `i32::MAX` (for nanos), respectively. 2. From `[email protected]` onward [`tendermint::abci::EventAttribute`](https://docs.rs/tendermint/0.36.0/tendermint/abci/enum.EventAttribute.html) became an enum with variants `V037` and `V034`, and introduced the fallible accessors `EventAttribute::key_str` and `EventAttribute::value_str`, in addition to the infallible `EventAttribute::key_bytes` and `EventAttribute::value_bytes`. This required changes in many `TryFrom<Event>` impls that would previously match on `&str` keys and directly move (or parse) `String` values. I chose to avoid extra error handling, instead matching on byte-string using `value_bytes()` (e.g. now `b"packet_src_channel" => {}` instead of the previous `"packet_src_channel" => {}`), and relying on `String::from_utf8_lossy` for the values.
- Loading branch information
1 parent
4cd8fc0
commit 0abbaeb
Showing
17 changed files
with
819 additions
and
493 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.