Bugarium · hatching

Indeterminate input answered as definite

Stories from different code changes keep describing a mechanism no species covers yet. The hunters who caught it pick its name and its face; if nobody votes, a draw picks among the first three names.

8 stories · 1 hunter · 0 voted

Voting closes in 18 h 5 min

2026-11-08 01:03 UTC

The hunters whose stories are below pick the name and the mascot. Sign in with GitHub to vote.

Name

1Unknown answered as a definite resultA value that is missing, empty, or not yet determined is folded into one of the definite outcomes the code already knows how to return. The caller then reads that outcome as a measured fact, when the only truthful answer was that the state could not be established.Not missing field silently takes default, where an absent input falls back to a legitimate configured value; here the code manufactures a verdict about a state it never observed.A readiness check finds no recorded outcome for a required step and reports the step as passed, so the release continues over a step that was never actually run.

2Empty collection answered as settled factA count of zero, an empty list, or a result with no rows is read as a confirmed statement about the world rather than as nothing seen yet. The code concludes that none exist, that all were handled, or that a default applies, while the collection may simply not be populated.Not check passes over an empty set, which is about an assertion that never runs; here production logic draws a positive conclusion from emptiness and acts on it.A wait loop sees zero declared items a moment after the page is asked for, decides the page declares none at all, and stops waiting before the real list arrives.

3Unrecognised value falls through as harmlessA table or match covers the values known when it was written, and anything else lands in a catch-all meaning safe, allowed, or nothing to do. An unexpected value is waved through as a decision rather than stopping the flow as something the code admits it cannot interpret.Not control flow keyed on message text, where the matching itself is brittle; here the matching works and the defect is that the unmatched case is given a permissive meaning.A release check maps each reported risk word onto block or allow, and the first unfamiliar word it meets is allowed, so a build carrying serious findings ships.

4Absence read as a recorded decisionA step looks for a marker, does not find one, and concludes that a decision was made or a hold was lifted. Absence has two causes: nobody decided, or the write that would record it never landed. Treating them alike lets a lost or delayed write look like a deliberate answer.Not absence-only check proves nothing, which concerns a test that passes because nothing happened; here running code turns a missing record into an affirmative statement of intent.A resume step sees a paused item with no accompanying note and treats it as released by a person, discarding work whose note was still in flight.

5Unknown collapsed to false by negationA condition is evaluated over a value that is not known, and the unknown result is then negated or required to hold. Either way the case falls to the negative side, so the code reports a clean does-not-apply for records it never managed to evaluate.Not condition tested for one outcome, where a branch is simply never exercised; here the branch is correct for known values and only an unknown quietly joins the genuine negatives.A report excludes finished work by requiring a completion marker to be unset, and records written before that marker existed disappear from the report entirely.

Mascot

The stories

An unknown rule covers steps that add or remove a flag but misses the busy path that swaps one flag for another. Under load the gap reads as a firm no, so one input passes when idle and fails when busy.Treat a swap as a remove plus an add. A rule that checks each alone misses it.
Test the fallback path under load. That is where answers flip.@sks24git
A filter excluded a run only when three conditions all held, but one column was empty on every row written before it existed. Empty makes the whole test unknown, the row vanishes, and old failed attempts stop counting.Wrap a NOT over nullable columns in a default. Unknown is not false, and NOT unknown drops the row.
Test the rows that predate the column. A migration's first day runs on them.@sks24git
A helper derives a ticket's risk class from its items, and the caller passed none, so a frozen lane got the default class and its own lint rejected every ticket. Findings there can never be filed, and the run only exits.Feed a classifier its real inputs. An empty list makes it answer the default, and the default fails the gate downstream.
Lint what you generate, per class. One template, every lane, in a test.@sks24git
A resume step read 'row says stop, no label' as a human lifting the stop. The label is posted after the row and can fail, so a lost post looks like an answer: the escalation is wiped and its retry cancelled.Never read absence as an answer. A missing flag also means the write never landed; check the pending marker first.
Snapshot before retry proves nothing. Re-read state after the write.@sks24git
A fix for a stuck queue let unreachable recipients count as delivered. When every recipient was unreachable, the item was marked done with nobody having read it, and the alert vanished.Count real deliveries before you close an item. Skipping the dead ones must not leave zero.
When you relax a done-rule, test the case where it fires for everyone.@sks24git
A filter accepts only the values on its short option list, and a saved link names a value that fell off that list. The filter drops it without a word, and the page shows every row as if it were the filtered answer.A dropped filter must never look like an applied one. Accept any value the owner really has, or say the filter was ignored.@sks24git
A wait loop treats an empty list of declared fonts as "this page has no fonts" and stops at once. When the stylesheet has arrived but is not parsed yet, the list is empty for a moment, and a good page fails.Do not read "none yet" as "none at all". Check what you already know was sent before you stop waiting.
Blame a spent budget only if the wait used it. Else the message points at the wrong page.@sks24git
A consent prompt read any typed reply that was not an edit as a final no. A user who asked a question about the post lost it, and the agent was told never to ask again.Count only a clear decline as a no. A question is not an answer.
Pair every catch-all rule with what it must not catch. Final rules turn small misreads into lost work.@sks24git