-
Notifications
You must be signed in to change notification settings - Fork 879
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
rustup update nightly sometimes doesn't see the most recent tarball #833
Comments
This seems like a caching Problem: Using Chrome to download, https://static.rust-lang.org/dist/channel-rust-nightly.toml contains sections like [pkg.rust.target.x86_64-apple-darwin]
available = true
url = "https://static.rust-lang.org/dist/2016-11-22/rust-nightly-x86_64-apple-darwin.tar.gz"
hash = "e969929b629d5519525be3c43e858d64c8696b35d8f899a6af89a93897d327e2" Whereas using [pkg.rust.target.x86_64-apple-darwin]
available = true
url = "https://static.rust-lang.org/dist/2016-11-21/rust-nightly-x86_64-apple-darwin.tar.gz"
hash = "1ef354dabd1747601ae0343e345186d6e1cd23f6d7376ad9b464b898aba861a7" Adding |
From the Cloudfront docs at http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/ServingCompressedFiles.html, it seems that the compressed / non-compressed caches are separate:
This sounds to me like this might be a bug with CloudFront + S3 + CF Compression + CF Invalidation |
By the way, here are the response headers:
|
This is likely a dupe of rust-lang/rust#21239 |
@alexcrichton: Ah, I though there was already an invalidation step on the nightly builders, which just wasn't working correctly. |
Oh I see. |
This seems to be happening again @alexcrichton? $ curl -s https://dev-static.rust-lang.org/dist/channel-rust-nightly.toml | grep -B1 version
date = "2017-05-07"
manifest-version = "2"
--
[pkg.cargo]
version = "0.19.0-nightly (fa7584c14 2017-04-26)"
--
[pkg.rls]
version = "0.1.0-nightly (67babd2d6 2017-04-27)"
--
[pkg.rust]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rust-analysis]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rust-docs]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rust-mingw]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rust-src]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rust-std]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
--
[pkg.rustc]
version = "1.19.0-nightly (5b31bf851 2017-05-07)"
$ rustup update
info: syncing channel updates for 'stable-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'beta-x86_64-unknown-linux-gnu'
info: syncing channel updates for 'nightly-x86_64-unknown-linux-gnu'
stable-x86_64-unknown-linux-gnu unchanged - rustc 1.17.0 (56124baa9 2017-04-24)
beta-x86_64-unknown-linux-gnu unchanged - rustc 1.18.0-beta.1 (4dce67253 2017-04-25)
nightly-x86_64-unknown-linux-gnu unchanged - rustc 1.19.0-nightly (f4209651e 2017-05-05) |
Ahhh, never mind, I was looking at |
Today,
rustup update nightly
gives the same version asnightly-2016-11-21
even thoughnightly-2016-11-22
exists.The text was updated successfully, but these errors were encountered: