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
You can find the proposed fix in rust-lang/cargo#3898. I tried to get rid of quick fixes and implement a full featured solution for inferring bin target's source file paths. Please review the inferring logic — I am not 100% sure that it covers all cargo's usecases, but it seems reasonable for me.
Activity
jethrogb commentedon Mar 31, 2017
What do you mean source is not available? How did you find the regression in the first place?
brson commentedon Apr 1, 2017
@jethrogb I mean that I can't find the git repo. The source can be acquired from the published crate tarball.
Edit: er, I didn't file this bug, but that's what @alexcrichton meant.
patrickjm commentedon Apr 2, 2017
The repo has been deleted for some time now - I tried to delete it from cargo but that's not allowed.
brson commentedon Apr 2, 2017
Should probably still be investigated, unless @patrickjm doesn't want us testing his yanked crate. We'll have to grab it from crates.io.
I wonder if maybe cargobomb shouldn't test yanked crates.
alexcrichton commentedon Apr 3, 2017
This is a regression in Cargo. With a
Cargo.tomlthat looks like:And files at
src/main.rsandsrc/foo.rson stable Cargo will compilesrc/main.rs, on beta Cargo will compilesrc/foo.rsinstead.cc @jmatraszek, is this related to rust-lang/cargo#3609 perhaps?
jmatraszek commentedon Apr 4, 2017
Hi @alexcrichton, will investigate this today, but looks like it is related.
alexcrichton commentedon Apr 4, 2017
Thanks @jmatraszek!
patrickjm commentedon Apr 4, 2017
Sorry about the hassle guys. I removed it because I didn't want my useless and dead project polluting things up, but that just caused more trouble!
No worries about testing my yanked crate. @brson
alexcrichton commentedon Apr 4, 2017
@patrickjm oh no worries! This crate helped us detect a regression and what's what we're worried about :)
jmatraszek commentedon Apr 4, 2017
Hi @alexcrichton,
I think this was caused by this: https://github.com/rust-lang/cargo/blob/master/src/cargo/util/toml.rs#L1367, but it worked because of the bug I fixed in 3609 (cargo always assumed
src/main.rsas a source file for a bin target).You can find the proposed fix in rust-lang/cargo#3898. I tried to get rid of quick fixes and implement a full featured solution for inferring bin target's source file paths. Please review the inferring logic — I am not 100% sure that it covers all cargo's usecases, but it seems reasonable for me.
alexcrichton commentedon Apr 4, 2017
Awesome thanks for the investigation @jmatraszek!
Auto merge of #3898 - jmatraszek:fix_rust_40955, r=alexcrichton
Update cargo submodules
Rollup merge of rust-lang#41166 - alexcrichton:update-cargo, r=brson
Rollup merge of rust-lang#41166 - alexcrichton:update-cargo, r=brson
Rollup merge of rust-lang#41166 - alexcrichton:update-cargo, r=brson