failure while fetching: uri changed final destination during transfer #1004
Labels
No labels
Affects/CppNix
Affects/Nightly
Affects/Only nightly
Affects/Stable
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/lix ci
Area/nix-eval-jobs
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/repl/debugger
Area/store
bug
Context
contributors
Context
drive-by
Context
maintainers
Context
RFD
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
Feature/S3
imported
Language/Bash
Language/C++
Language/NixLang
Language/Python
Language/Rust
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
Topic/Large Scale Installations
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#1004
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Describe the bug
I have seen a failure like this a couple of times now on GHC's CI while fetching:
See for instance: https://gitlab.haskell.org/ghc/head.hackage/-/jobs/2311058
I'm not sure if this is a bug in Lix proper or something wrong with the CI environment in which it is running.
We are running Lix-2.93.3 using the official Docker image.
Steps To Reproduce
As far as I can tell the error is not easily reproducible and intermittent.
We have only seen it twice.
Expected behavior
We shouldn't error if GitHub decides that it wants to redirect us quite oddly mid transfer like this.
Lix version
2.93.3 using the official docker image
this is github redirecting a download of a file to two different urls depending on ... something. today we reject such redirects because they're an easy cause of undetectable corruption, but perhaps the error should be downgraded to a warning