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
> cargo tree -i -p untrusted
error: There are multiple `untrusted` packages in your project, and the specification `untrusted` is ambiguous.
Please re-run this command with `-p <spec>` where `<spec>` is one of the following:
https://github.com/briansmith/untrusted#0.6.2
https://github.com/briansmith/untrusted#0.6.2
As you see, the versions are identical but cargo seems not to realize that
This issue causes errors like
--> /home/brenzi/.cargo/registry/src/github.com-1ecc6299db9ec823/libp2p-core-0.7.1/src/identity/rsa.rs:74:27
|
74 | Input::from(msg),
| ^^^^^^^^^^^^^^^^ expected struct `untrusted::Input`, found a different struct `untrusted::Input`
|
= note: expected type `untrusted::Input<'_>` (struct `untrusted::Input`)
found type `untrusted::Input<'_>` (struct `untrusted::Input`)
note: Perhaps two different versions of crate `untrusted` are being used?
I assume this is caused by a patch statement in workspace Cargo.toml
I get the following funny behaviour:
As you see, the versions are identical but cargo seems not to realize that
This issue causes errors like
I assume this is caused by a patch statement in workspace Cargo.toml
which is needed because otherwise two truly different versions of
untrusted
would collide.Here's my repo showing this behaviour: https://github.com/scs/substraTEE-worker/tree/brenzi-ra
The text was updated successfully, but these errors were encountered: