Stream: warg

Topic: Warg changes may have broken cargo-component

Daniel Macovei (May 11 2023 at 17:31):

When I run cargo install --git https://github.com/bytecodealliance/cargo-component I get the following error:

error[E0432]: unresolved import `warg_client::storage::PackageStorage`
  --> src/registry.rs:24:44
   |
24 |     storage::{ContentStorage, PackageInfo, PackageStorage},
   |                                            ^^^^^^^^^^^^^^ no `PackageStorage` in `storage`

error[E0599]: no method named `packages` found for reference `&warg_client::Client<FileSystemPackageStorage, FileSystemContentStorage>` in the current scope
   --> src/registry.rs:740:30
    |
740 |                 match client.packages().load_package(id.as_str()).await? {
    |                              ^^^^^^^^ method not found in `&warg_client::Client<FileSystemPackageStorage, FileSystemContentStorage>`

I think it's because of the changes I recently made to warg, though I'm not sure if we do publishes manually or automatically in the project. I definitely got rid of PackageStorage in my most recent changes and now we use RegistryStorage. I can try and open a PR in cargo-component to fix this if people like?

Brian (May 11 2023 at 17:50):

Makes sense! We should probably add --locked to the install instructions in the README too until the deps are pointing to released versions.

Robin Brown (May 11 2023 at 18:00):

There is an issue on the repo documenting this

Robin Brown (May 11 2023 at 18:00):

https://github.com/bytecodealliance/cargo-component/issues/77#issuecomment-1542600794

Daniel Macovei (May 11 2023 at 18:24):

https://github.com/bytecodealliance/cargo-component/pull/78 should fix

Last updated: Dec 23 2024 at 12:05 UTC