'Graceful' fallback when one or more substituters fail #1061
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
awaiting
author
awaiting
contributors
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
lix-project/lix#1061
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?
Is your feature request related to a problem? Please describe.
Yes, nix/lix entirely fails if one or more subsituters isn't reachable. This was fixed upstream in cppnix with this PR: https://github.com/nixos/nix/pull/13301
Describe the solution you'd like
A fallback to other substituters, or just plain copying upstream's solution would be nice.
Describe alternatives you've considered
uh, switching back to cppnix?????? /hj
Additional context
N/A
@cyrneko do you have a reproducer? I closed a similar issue recently because I was unable to reproduce this issue on modern Lix.
I can give https://git.vulpecula.zone/tasiaiso/nixos-config, where it happens when
cache.vulpecula.zoneis down