-
Notifications
You must be signed in to change notification settings - Fork 104
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
Erroneous aliases for async-global-executor-1.4.2 #269
Comments
I think I have honed in on this one and should have a fix shortly, the downside is it relates to #187 and will be a bit of a rework |
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
…kages There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunatly, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targetting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of sublte aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
When using Tokio 1.0, this aliasing bug now also triggers on async-compression 0.3.7, a dependency of reqwest 0.11.0 which itself is a fairly popular library. As more and more libraries migrate to Tokio 1.0, I expect this issue will start cropping up for people with increasing frequency. No doubt the completion and merging of #282 would bring great rejoicing! 😄 In the meantime, an ugly hack to work around this is to use raze crate settings to skip and immediately re-add the Tokio dependency, e.g.: [package.metadata.raze.crates.async-compression.'*']
skipped_deps = ["tokio-1.0.1"]
additional_deps = ["@raze__tokio__1_0_1//:tokio"] This seems to trigger cargo-raze to elide the aliases on the tokio package, which allows compilation to continue in my particular case. |
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
There are a range of subtle and irritating bugs that stem from attempting to work with renames from the package set provided by cargo metadata. Fortunately, recent versions of cargo metadata provide a limited version of the resolve nodes, both as the original node ids and as a newer set providing both rename and targeting information. As such we can (hopefully) simplify crate -> dep node resolution, remove a bunch of subtle aliasing bugs. Fixes google#241, fixes google#269, fixes google#270, resolves google#144, resolves google#187
Repro:
Add a dependency on the crate async-global-executor-1.4.2 (https://github.com/async-rs/async-global-executor/blob/master/Cargo.toml).
That has this section in the
Cargo.toml
file:However, the file generated by
cargo raze
(v0.6.1, installed a few moments ago) looks like:Note the
aliases
section at the bottom, and howtokio_0_2_22
points totokio03_crate
, resulting in the following build error:Changing that
tokio03_crate
totokio02_crate
is enough for the build to succeed.The text was updated successfully, but these errors were encountered: