From 032c6519b2e0e5dc6d91769bfcc08a2f3d6c8b6c Mon Sep 17 00:00:00 2001 From: Niclas Overby Date: Tue, 11 Aug 2026 23:20:43 +0200 Subject: [PATCH] docs(cider): say what belongs in the run-status other bucket, since an unclassified count misleads The reader splits builders into producers, emitted and lowered, and everything else falls into other. That bucket had no documented contents, which is the shape of a number that quietly stops meaning anything: if it grows, nobody knows whether that is normal. Read off the last full run rather than guessed. All four were expected: cider-pin-pins-bootstrap_cmds the patched pin materialize-pins the pin assembly cider-dyn-gen-pairs the comparison input cider-dyn-gen-all the check itself So the header now says it should stay in the single digits, names those four, and says what to do if it grows into the dozens: look at the names before trusting the other three counts, because that means something is being built that none of the patterns recognises. Re-ran the script against the same log after the edit and the counts are unchanged, 4,516 builders split 1474 producers, 1474 emitted, 1564 lowered, 4 other, 0 errors. --- scripts/buck-run-status.nu | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/scripts/buck-run-status.nu b/scripts/buck-run-status.nu index ee813892e..25c429354 100755 --- a/scripts/buck-run-status.nu +++ b/scripts/buck-run-status.nu @@ -17,6 +17,19 @@ # Seeing all three at once is correct when both routes are being built, and is exactly what a # run after a source change looks like. # +# WHAT BELONGS IN "other", because an unclassified bucket is how a counter quietly misleads. +# It should stay in the single digits and hold the things that are neither route: the pin +# derivations and whatever check sits at the top. Read off the last full run rather than +# guessed, where all four were expected: +# +# cider-pin-pins-bootstrap_cmds the patched pin +# materialize-pins the pin assembly +# cider-dyn-gen-pairs the comparison input +# cider-dyn-gen-all the check itself +# +# If this number grows into the dozens something is being built that none of the three +# patterns recognises, and the fix is to look at the names before trusting the other counts. +# # COUNT WHAT RAN, NEVER THE WILL-BE-BUILT LIST. nix prints "these N derivations will be built" # and then may build none of them, because a content addressed placeholder always moves even # when the output does not. Only `building '...'` lines mean a builder started. -- 2.51.2