Figure out what want-mass-query does and potentially remove it? #394
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
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: lix-project/lix#394
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?
As far as I can tell,
want-mass-query
affects exactly one conditional here:b8cb7abcf0/src/libstore/local-store.cc (L1087)
Notably, there are other cases where we call
queryValidPaths
, so I don't know why it is behind a setting for substitution. I am guessing it might be related to very busted store backends like the ssh one that have horrible latency.The only thing that actually calls this functionality is
--prebuilt-only
and picking versions innix-env
. Which, uhhhhhhhhhhh. This is very badly documented. Also, part of its use innix-env
is mildly horrifying: it selects derivation versions by substitutability. I could see it being reasonable for stuff like Haskell where there's one preferred version that is built, and the others aren't, but, man this is a bad idea.Is this why
nix-env -i
without-A
is so slow?! Wow.