Lix v2.91: nix commands, that include nixpkgs evaluation, are followed by flashing messages about copying some default hooks from nixpkgs into the store #561

Closed
opened 2024-10-28 20:40:56 +00:00 by acid-bong · 3 comments

Describe the bug

Here's asciinema recording of this: https://asciinema.org/a/EYQDFElEiAdXiQL6Mo3hsIdo5
Since the recording is gone, i'll describe this in words: there are flashing messages when i'm running something that evaluates a derivation, be it nix flake check or nix build|run|shell|develop.

Steps To Reproduce

  1. nix shell nixpkgs#lixVersions.lix_2_91
  2. nix run nixpkgs#hello

Expected behavior

Just like in Nix or Lix v2.90, there should be no flashing messages.

nix --version output

nix (Lix, like Nix) 2.91.1

## Describe the bug ~~Here's asciinema recording of this: https://asciinema.org/a/EYQDFElEiAdXiQL6Mo3hsIdo5~~ Since the recording is gone, i'll describe this in words: there are flashing messages when i'm running something that evaluates a derivation, be it `nix flake check` or `nix build|run|shell|develop`. ## Steps To Reproduce 1. `nix shell nixpkgs#lixVersions.lix_2_91` 2. `nix run nixpkgs#hello` ## Expected behavior Just like in Nix or Lix v2.90, there should be no flashing messages. ## `nix --version` output nix (Lix, like Nix) 2.91.1
acid-bong added the
bug
label 2024-10-28 20:40:56 +00:00
acid-bong changed title from Lix v2.91: `nix build|run|shell` is followed by flashing messages about copying some default hooks from nixpkgs into the store to Lix v2.91: nix commands, that include nixpkgs evaluation, are followed by flashing messages about copying some default hooks from nixpkgs into the store 2024-10-30 10:58:00 +00:00
Author

Ight, I did the bisection between 2.90.0 and 2.91.0, the culprit is the multiline format commit (da4e46dd1f). This behaviour is present both by default (I assume nix3 commands use --log-format bar) and when --log-format multiline is specified.

cc @kloenk (the author), @Qyriad and @pennae (the reviewers)

Ight, I did the bisection between 2.90.0 and 2.91.0, the culprit is the multiline format commit (da4e46dd1fc04067b5ba4bc16dd68134fa7efad2). This behaviour is present both by default (I assume `nix3` commands use `--log-format bar`) and when `--log-format multiline` is specified. cc @kloenk (the author), @Qyriad and @pennae (the reviewers)
Member

This issue was mentioned on Gerrit on the following CLs:

  • commit message in cl/2174 ("libmain/progress-bar: actually don't show short activities")
<!-- GERRIT_LINKBOT: {"cls": [{"backlink": "https://gerrit.lix.systems/c/lix/+/2174", "number": 2174, "kind": "commit message"}], "cl_meta": {"2174": {"change_title": "libmain/progress-bar: actually don't show short activities"}}} --> This issue was mentioned on Gerrit on the following CLs: * commit message in [cl/2174](https://gerrit.lix.systems/c/lix/+/2174) ("libmain/progress-bar: actually don't show short activities")
Author

The fix actually works, thx a lot

The fix actually works, thx a lot
Sign in to join this conversation.
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#561
No description provided.