Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build errors through failure #134

Closed
mpapierski opened this issue Dec 11, 2018 · 3 comments
Closed

Build errors through failure #134

mpapierski opened this issue Dec 11, 2018 · 3 comments

Comments

@mpapierski
Copy link

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/github.com-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.

@atoav
Copy link

atoav commented Dec 11, 2018

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)

@aleksuss
Copy link

@alexcrichton
Copy link
Member

I'm going to close this since I believe it was fixed with 0.3.11

@vlisivka are you perhaps using an outdated rustc? If not, mind opening a dedicated issue with some more info?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants