cosmrs 0.4.0: "failed to resolve: could not find `v1` in `wasm`" about cosmos-rust HOT 6 CLOSED

This seems to have happened because the cosmos-sdk-proto crate is included via a path; this is hiding the fact that the crate will reference the published version elsewhere, but not when built locally. To reproduce, you can apply this diff:

diff --git a/cosmrs/Cargo.toml b/cosmrs/Cargo.toml
index bbfa8ee..d3b75d8 100644
--- a/cosmrs/Cargo.toml
+++ b/cosmrs/Cargo.toml
@@ -12,7 +12,7 @@ edition = "2021"
 rust-version = "1.56"

 [dependencies]
-cosmos-sdk-proto = { version = "0.8", default-features = false, path = "../cosmos-sdk-proto" }
+cosmos-sdk-proto = { version = "0.8", default-features = false }
 ecdsa = { version = "0.13", features = ["std"] }
 eyre = "0.6"
 k256 = { version = "0.10", features = ["ecdsa", "sha256"] }

And then try to run the tests.

It might be worth decoupling the publishing process for these two crates to prevent this in the future.

from cosmos-rust.

I was literally about to post the same issue here as I attempted to build using version 0.4.0 : )

What seems that has happened is that even though a new version of cosmrs was released, nothing was done [in terms of releases] for the cosmos-sdk-proto crate, even though it got changed between cosmrs 0.3.0 and 0.4.0. The notable difference includes the protobuf path changes:

cosmrs 0.3.0:

pub mod cosmwasm {
    /// Messages and services handling CosmWasm.
    pub mod wasm {
        pub mod v1beta1 {
            include!("prost/cosmwasm.wasm.v1beta1.rs");
        }
    }
}

cosmrs 0.4.0

pub mod cosmwasm {
    /// Messages and services handling CosmWasm.
    pub mod wasm {
        pub mod v1 {
            include!("prost/cosmwasm.wasm.v1.rs");
        }
    }
}

Thus, it would be amazing if cosmos-sdk-proto was updated to 0.9 and was put into cosmrs 0.4.1 release.

from cosmos-rust.

I agree with your assessment. PR to release cosmos-sdk-proto v0.9 here: #167

from cosmos-rust.

I'd recommend not relying on path when publishing, otherwise it's difficult to detect these discrepancies between published and unpublished changes in deps.

from cosmos-rust.

I'd recommend not relying on path when publishing

What are you suggesting exactly? Removing it to publish, then always following up with another commit to add it back? Seems tedious.

from cosmos-rust.

Fixed by #168

from cosmos-rust.