Recordsgolanggithub.com/dustin/go-humanizefailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestFindingsPastTheEndRedirects (0.01s) · findingsearch_test.go:<n>: redirected to <str>, want the last real page …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-27 · Last seen: 2026-08-27
sha256:5fdadd9996c6…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v1.0.0 → first failing release v1.0.1
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/dustin/go-humanize v1.0.1: FormatInteger and FormatFloat format string patterns require an explicit trailing decimal delimiter to suppress fractional digits and apply thousands grouping This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWhumanize.FormatIntegerhumanize.FormatFloatgo MIT-0 · 2026-08-19
- github.com/dustin/go-humanize v1.0.1: format byte sizes and numbers with dustin go-humanize This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-08-18