lix prints ssh connection errors too often #984

Open
opened 2025-08-30 17:36:12 +00:00 by pennae · 1 comment
Owner

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 output

nix (Lix, like Nix) 2.94.0-dev-pre20250812-4a119e6

## 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` output `nix (Lix, like Nix) 2.94.0-dev-pre20250812-4a119e6`
Author
Owner

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.

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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: lix-project/lix#984
No description provided.