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
error[E0599]: the method `as_dyn_error` exists for reference `&ParseError`, but its trait bounds were not satisfied --> /home/sky9/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/cargo-dist-0.28.0/src/errors.rs:74:13 |74 | #[error(transparent)] | ^^^^^^^^^^^ method cannot be called on `&ParseError` due to unsatisfied trait bounds | ::: /home/sky9/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/target-lexicon-0.12.16/src/parse_error.rs:8:1 |8 | pub enum ParseError { | ------------------- doesn't satisfy `_: AsDynError<'_>` or `_: Error` | = note: the following trait bounds were not satisfied: `cargo_dist_schema::target_lexicon::ParseError: StdError` which is required by `cargo_dist_schema::target_lexicon::ParseError: AsDynError<'_>` `&cargo_dist_schema::target_lexicon::ParseError: StdError` which is required by `&cargo_dist_schema::target_lexicon::ParseError: AsDynError<'_>`For more information about this error, try `rustc --explain E0599`.error: could not compile `cargo-dist` (lib) due to 1 previous errorerror: failed to compile `cargo-dist v0.28.0`, intermediate artifacts can be found at `/tmp/cargo-installB7Xz8H`.To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
The issue seems to be related to the target-lexicon crate.
The unlocked build compiles both target-lexicon versions 0.12.16 AND 0.13.2, but the --locked install (which works) only builds v0.12.16.
Cloning the current repo, running cargo update and then cargo build fails with the same error.
cargo install [email protected]
:The issue seems to be related to the target-lexicon crate.
The unlocked build compiles both
target-lexicon
versions 0.12.16 AND 0.13.2, but the --locked install (which works) only builds v0.12.16.Cloning the current repo, running
cargo update
and thencargo build
fails with the same error.Before:
After:
Output of running cargo update
The text was updated successfully, but these errors were encountered: