Lock paths can become too long when remote builders are involved #157
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#157
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?
Running
installChecks
ondea029ff51
causes an error due to using the ridiculously long lockfile path of:This should likely be replaced by a hash instead so that the name cannot become absurdly long.
Why does the entire remote builder configuration get encoded into a lockfile path in the first place??
See https://git.lix.systems/lix-project/lix/src/branch/main/src/build-remote/build-remote.cc#L40 and https://git.lix.systems/lix-project/lix/src/branch/main/src/build-remote/build-remote.cc#L266
O_o
simply sha256 the normalized url and take some prefix or so
From Nixpkgs' definition of the Nix package:
Wonder if this is relevant.
honestly we should just fix this in a generalized manner by hashing the path though (maybe minus one component? maybe print out the full name so you can find which process was doing it? just to not regress the ability to find who is holding a lock)