name paths for purity, preventing double-hash store paths #346
No reviewers
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: sysadmin
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Fediversity/Fediversity#346
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "kiara/Fediversity:purge-double-hash"
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?
see https://github.com/NixOS/nix/issues/10627
Is this solving some issue we had?
@fricklerhandwerk this should be noticeable only after #92; the impurity makes it less cacheable as the hash would depend on the root directory name.
so no more urgent than that.
d4cbc915cd
to0c30914acb
0c30914acb
to43c64debfc
43c64debfc
to5e887094c3
I really don't know whether the decrease in readability is worth the questionable increase in caching. I see that for
shell.nix
it would slightly improve the situation if a contributor happened to change the containing directory's name, but otherwise? @Niols Is the double-hashed-storepath actually a thing for the deployment test? Or could the explicit store path name be isolated to just the test code? Would it maybe get solved by moving the test flakes to the VM test rather than re-using the main flake?i do suppose even if top-level caching is beaten by this, caching of dependency derivations should be fine still, so i'd be okay with closing if preferred
Pull request closed