nix.md: name the fired assertion; messages are not derivation inputs #66
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/memory!66
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/session-lessons-witness-and-comments"
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?
Summary
Two additions to
nix.mdand two ledger sightings from the allod/archetypes#70, #106, #114 session. Nothing a machine runs changes. If either note proves wrong, edit or delete the paragraph.nix.md, "Reading a config option does not force NixOS assertions": how to write a negative fixture that names which assertion fired (readconfig.assertions, filter for!assertion), and that reading activation text orage.secretsforces nothing. This is what allod/archetypes#114 found: a check that had never run its module's assertions.nix.md, new "An assertion message is not a derivation input": an eval-time message edit leaves every derivation path unchanged while a builder-script message moves it, so the derivations-unchanged witness can confirm the former did nothing and cannot show it happened. Learned across #112, #113 and #115, where 24 message edits moved 4 derivations.ledger.md: twoignoredsightings, the comment-policy line (the owner had to ask for a trim) and the assertions-forcing line (the Pi check).R0, docs only.