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
Apologizes if this is incorrect repo to report such things. Probably I should report in both affected repos.
I'm using failure = 0.1.3 and after cargo update backtrace got resolved to 0.3.10 which is released today. And all of sudden I can't build failure because:
Compiling failure v0.1.3
error[E0034]: multiple applicable items in scope
--> /home/michal/.cargo/registry/src/git.luolix.top-1ecc6299db9ec823/failure-0.1.3/src/backtrace/mod.rs:132:20
|
132 | bt.fmt(f)
| ^^^ multiple `fmt` found
|
= note: candidate #1 is defined in an impl of the trait `std::fmt::Debug` for the type `backtrace::backtrace::Backtrace`
= note: candidate #2 is defined in an impl of the trait `std::fmt::Display` for the type `backtrace::backtrace::Backtrace`
Looks like backtrace introduced some backwards incompatible change, or failure needs to be updated to accomodate for changes in backtrace.
For now cargo update -p backtrace --precise 0.3.9 solves the build issue, but as I'm developing a lib crate my travis builds will fail.
The text was updated successfully, but these errors were encountered:
Could reproduce the same issue in a minimal environment (the default cargo new- hello world with extern crate failure and failure="0.1.3" in Cargo.toml)
Apologizes if this is incorrect repo to report such things. Probably I should report in both affected repos.
I'm using
failure = 0.1.3
and aftercargo update
backtrace got resolved to0.3.10
which is released today. And all of sudden I can't build failure because:Looks like backtrace introduced some backwards incompatible change, or failure needs to be updated to accomodate for changes in backtrace.
For now
cargo update -p backtrace --precise 0.3.9
solves the build issue, but as I'm developing a lib crate my travis builds will fail.The text was updated successfully, but these errors were encountered: