Recordsgolanggithub.com/huandu/xstringsfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: undefined: xstrings.LevenshteinDistance · test/contract.go:<n>:<n>: undefined: xstrings.LevenshteinDistance …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:5e514a4c0cfc…
github.com/huandu/xstrings.LevenshteinDistance github.com/huandu/xstrings.Reverse github.com/huandu/xstrings.WordWrap
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/huandu/xstrings v1.5.0 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-21