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
Labels
No labels
Area/build-packaging
Area/cli
Area/evaluator
Area/fetching
Area/flakes
Area/language
Area/profiles
Area/protocol
Area/releng
Area/remote-builds
Area/repl
Area/store
bug
crash 💥
Cross Compilation
devx
docs
Downstream Dependents
E/easy
E/hard
E/help wanted
E/reproducible
E/requires rearchitecture
imported
Needs Langver
OS/Linux
OS/macOS
performance
regression
release-blocker
RFD
stability
Status
blocked
Status
invalid
Status
postponed
Status
wontfix
testing
testing/flakey
ux
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#561
Loading…
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
Here's asciinema recording of this: https://asciinema.org/a/EYQDFElEiAdXiQL6Mo3hsIdo5Since 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
ornix build|run|shell|develop
.Steps To Reproduce
nix shell nixpkgs#lixVersions.lix_2_91
nix run nixpkgs#hello
Expected behavior
Just like in Nix or Lix v2.90, there should be no flashing messages.
nix --version
outputnix (Lix, like Nix) 2.91.1
Lix v2.91: `nix build|run|shell` is followed by flashing messages about copying some default hooks from nixpkgs into the storeto Lix v2.91: nix commands, that include nixpkgs evaluation, are followed by flashing messages about copying some default hooks from nixpkgs into the storeIght, 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 assumenix3
commands use--log-format bar
) and when--log-format multiline
is specified.cc @kloenk (the author), @Qyriad and @pennae (the reviewers)
This issue was mentioned on Gerrit on the following CLs:
The fix actually works, thx a lot