Bad error message when untracked files are present #570
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
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#570
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 untracked files are present in the current repository, flake commands like
nix build
,nix develop
, andnix run
won't copy the files into the Nix store before evaluating, leading to unclear error messages. For example, here's the error message when a filetfc-workspace-deps-twice
isn't staged:Note that
Function called without required argument "tfc-workspace-deps-twice"
makes no mention of a filetfc-workspace-deps-twice.nix
. This is one of those error messages that new users just have to learn means something completely different than what it says.Expected behavior
There should be a clear and difficult-to-ignore message saying that a file
tfc-workspace-deps-twice.nix
is untracked and therefore not being copied into the Nix store.nix --version
outputAdditional context
Upstream:
Note that
git add --intent-to-add
/git add -N
will stage the file enough for Lix to pick it up.It might be nice to save warnings and replay them at the end of evaluation; warnings typically occur at the start of a large block of output and therefore are easily ignored.
related #175