-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Regression in asynchronous-0.4.5, Rust 1.17 #40953
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
Comments
Also affects error-chain cc @Yamakaky |
Like also affects error_defs cc @canndrew |
Also fiber cc @TileHalo |
Also gimli cc @fitzgen |
Also futures 0.1.0 |
Also libimagstore |
I pinged @aturon about this a few weeks ago. Then I landed a commit to work around the regression within gimli and a new version published to crates.io. Are you saying that the most recent version on crates.io is still affected (or that perhaps this is a different-but-similar regression)? Are the crates listed here the results of a crater (or its new replacement whose name I forgot)? |
@fitzgen these results are from cargobomb (a crater equivalent-ish) and the full results are posted online with the two regression logs for gimli, downloaded from crates.io. Do you remember why this fix was needed? It'd be good to track down why inference started failing to see if we want to revert that change. |
I modified the broken test from error-chain so that it doesn't fail anymore, BTW. But thanks for the ping. |
@Yamakaky can you point to the fix? It's not clear to me at least currently why this regression happened and affected so many crates. |
This may be fixed by #40636 -- which has yet to be backported to beta. |
Here is the gimli fix I had made: gimli-rs/gimli@dbec032 |
Thanks for looking into this Niko! Thanks also for the links to fixes, let's land the backport and go from there |
…chton Backport #40636 to beta I suspect that this will help with #40953 but have not been able to verify for...reasons. r? @alexcrichton cc @brson
OK, so, the backport landed. @alexcrichton, when do you think we'll spin off a new beta so we can most easily test if this is fixed? (That is still a manual process, right?) |
@nikomatsakis we'll try to get a new beta scheduled today |
New beta is here and bug appears fixed! Closing. |
https://github.com/bcndanos/asynchronous
Not on nightly.
cc @bcndanos
The text was updated successfully, but these errors were encountered: