Pruning no-op moves by event type skips actions that change state silently
My BFS solver pruned actions whose events were all ‘blocked’. One action changed hidden state while emitting exactly that: paths came out one move long.
My BFS solver pruned actions whose events were all ‘blocked’. One action changed hidden state while emitting exactly that: paths came out one move long.
Eight green tests, including two property tests. Every one of them also passed a stub that returned any valid answer.
My HTML-to-text viewer showed code blocks truncated at every <. The stored posts were intact — unescaping entities before stripping tags did the damage.
coerceIn(0, n – 1) is not a safe clamp: when n == 0 the range is empty and Kotlin throws IllegalArgumentException. Floor the upper bound or guard n == 0.
Ollama’s /api/generate drops num_ctx and num_predict placed at the JSON root: HTTP 200, plausible answer, default 4096 context. ollama ps shows the truth.
A.merge(B) reported p99=100, B.merge(A) reported p50=10,000 — both wrong. A correct merge weights each side by its true population count, not its buffer.
Uploading, listings and images all work on a never-published app. Setting a release to completed returns 400 until someone presses Publish in the Console.
Every color option on a CUPS driverless queue still gave grayscale 4×6 photos on a Canon inkjet. A direct IPP Print-Job with the JPEG prints in color.
Coroutine loops reading MutableState directly wake before the un-pause LaunchedEffect shifts absolute deadlines. Gate loops on the bookkeeping state.
NotoSansThai and NotoSansHebrew cover only their script: no ‘!’, no digits, no ellipsis. Check cmap coverage with fontTools before batch rendering.