nix flake show
cancels the entire print if one item doesn't match the expected schema #768
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#768
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 running
nix flake show
on a flake that contains attributes that don't match what the Lix CLI tool expects to be in that place (eg. something that isn't a derivation indevShells.${system}
), Lix prints an error message (eg.error: expected a derivation
) and exits, without showing the rest of the outputs. This is annoying when I want to see other parts of the flake that Lix might be able to show with no problems, but it never prints them because an earlier failure in one path terminated the entire print.Steps To Reproduce
Using the Lix 2.92.0 release flake as an example:
nix flake show https://git.lix.systems/lix-project/lix/archive/2.92.0.tar.gz
devShells
Example output (with some omissions for brevity:
Expected behavior
I'd expect to see something like the following, where the error is logged for that one path and printing continues, eg.
nix --version
outputAlso reproducible on most recent stable release: