lix prints ssh connection errors too often #984
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#984
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
when a builder is offline or unreachable for other reasons we print an ssh unreachable error for it every time it is contacted. this is very noisy and doesn't tell us very much if the error message hasn't changed.
Steps To Reproduce
build something with many dependencies while any configured builder isn't reachable
Expected behavior
only print one unreachable error per builder
nix --version
outputnix (Lix, like Nix) 2.94.0-dev-pre20250812-4a119e6
this is mostly down to us being able to start multiple remote builds concurrently. we currently have a hard-coded limit of four concurrent attempts, which quadruplicates ssh error messages for offline builders. hiding these errors on subsequent attempts or marking a builder as offline and not trying to use it for a while requires a lot more work than is reasonable at this moment, and in any case becomes almost trivial once we have proper store rpc and can integrate remote builder management into the core (while retaining the ability to have build hooks the way they are now by configuring a single remote builder that points to the hook).
calling this not a release blocker, just a bit annoying.