Log why flake fetching is happening #216

New issue

Open

opened 2024-04-02 18:29:30 +00:00 by qyriad · 1 comment

qyriad commented

2024-04-02 18:29:30 +00:00

Owner

Flake inputs have to be downloaded before almost any Nix code is evaluated. Instead of just progress bars describing opaque paths that are being fetched we should log that we are fetching flake inputs, and what inputs are causing what fetches.

Flake inputs have to be downloaded before *almost* any Nix code is evaluated. Instead of just progress bars describing opaque paths that are being fetched we should log *that we are fetching flake inputs*, and what inputs are causing what fetches.

qyriad added the

Area/flakes

labels 2024-04-02 18:29:30 +00:00

roberth commented

2024-05-29 21:59:27 +00:00

The fetching is a bit indirect, happening through call-flake.nix, which in turn calls fetchTree. I suppose you could pass a secret flag or pass a special variant to call-flake.nix, but I think most of the value is in printing the URL, which I believe Nix has implemented after 2.18.

The fetching is a bit indirect, happening through `call-flake.nix`, which in turn calls `fetchTree`. I suppose you could pass a secret flag or pass a special variant to `call-flake.nix`, but I think most of the value is in printing the URL, which I believe Nix has implemented after 2.18.

No milestone

No project

No assignees

2 participants

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#216

No description provided.