[Nix#8721] Traces from errors in functions don't show the actual error location #130
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#130
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?
Upstream-Issue: NixOS/nix#8721
Describe the bug
It seems that at least when nested in functions, the actual error location, by far the most important piece of information, is not shown in the trace.
This work is sponsored by Antithesis ✨
Steps To Reproduce
Here's just
builtins.length "test"
, an obvious type error:Notice how it correctly shows the error occurring "while calling the 'length' builtin", along with the precise location of the builtin.
But now let's wrap it in a function:
Now the trace on the builtin isn't there anymore, the trace stops at the enclosing function call and doesn't show anything more detailed.
This makes it really hard to debug larger functions.
Expected behavior
The exact location of where the error occurred should be shown.
nix-env --version
outputnix-env (Nix) 2.15.1
Additional context
Priorities
Add 👍 to issues you find important.
Marking as release blocker because this sucks, but we can revisit that decision later.
this is fixed on main: