Recordsgolanggolang.org/x/textfailure issue
Failure signature
PROJECT_PROCESS Evidence gap ×6
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-26 · Last seen: 2026-08-27
golang.org/x/text/collate.Buffer golang.org/x/text/collate.New golang.org/x/text/currency.ParseISO golang.org/x/text/currency.Symbol golang.org/x/text/language.English golang.org/x/text/language.German golang.org/x/text/language.Swedish golang.org/x/text/message.NewPrinter golang.org/x/text/message.SetString golang.org/x/text/search.IgnoreCase golang.org/x/text/search.New golang.org/x/text/secure/precis.UsernameCaseMapped
Where it was measured
PASS means the release recorded a passing observation at PROJECT_PROCESS and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.35.0 PASS 214 passing observations
- v0.34.0 FAIL
- v0.33.0 PASS 19 passing observations
- v0.31.0 PASS 41 passing observations
- v0.29.0 FAIL
- v0.28.0 PASS 33 passing observations
- v0.23.0 FAIL
- v0.18.0 FAIL
- v0.14.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×6 2026-08-26 → 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 v0.13.0 → first failing release v0.14.0
What differs across the boundary
- golang.org/x/tools v0.14.0, v0.6.0 → v0.6.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.14.0 → first passing release v0.16.0
What differs across the boundary
- golang.org/x/tools v0.2.0, v0.21.1-0.20240508182429-e35e4ccd0d2d → v0.6.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.17.0 → first failing release v0.18.0
What differs across the boundary
- golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.18.0 → first passing release v0.20.0
What differs across the boundary
- golang.org/x/tools v0.47.0 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.22.0 → first failing release v0.23.0
What differs across the boundary
- golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d → v0.21.1-0.20240508182429-e35e4ccd0d2d, v0.31.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.23.0 → first passing release v0.24.0
What differs across the boundary
- golang.org/x/tools v0.21.1-0.20240508182429-e35e4ccd0d2d → v0.21.1-0.20240508182429-e35e4ccd0d2d, v0.31.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.28.0 → first failing release v0.29.0
What differs across the boundary
- golang.org/x/tools v0.35.0 → v0.36.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.29.0 → first passing release v0.31.0
What differs across the boundary
- golang.org/x/tools v0.38.0 → v0.36.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last passing release v0.33.0 → first failing release v0.34.0
What differs across the boundary
- golang.org/x/tools v0.40.0, v0.41.0 → v0.41.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.34.0 → first passing release v0.35.0
What differs across the boundary
- golang.org/x/tools v0.42.0 → v0.41.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v0.35.0 | v0.34.0 | v0.33.0 | v0.31.0 | v0.29.0 | v0.28.0 | v0.23.0 | v0.18.0 | v0.14.0 |
|---|---|---|---|---|---|---|---|---|---|
| golang.org/x/tools | v0.42.0 | v0.41.0 | v0.41.0 | v0.38.0 | v0.36.0 | v0.35.0 | v0.31.0 | — | v0.6.0 |
Moved: 1 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/text v0.34.0: collate.Collator.CompareString 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. HOWcollate.Collator.CompareStringgo 1.26 MIT-0 · 2026-08-26
- golang.org/x/text v0.34.0: message.SetString 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. HOWmessage.SetStringgo 1.26.6 MIT-0 · 2026-08-26
- golang.org/x/text v0.34.0: collate.Collator.Compare 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. HOWcollate.Collator.Compare MIT-0 · 2026-08-26
- golang.org/x/text v0.29.0: convert text to title case using language-specific casing rules 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. HOWgolang.org/x/text/cases.Titlegolang.org/x/text/language.Tag MIT-0 · 2026-08-18
- golang.org/x/text v0.23.0: language.English 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. HOWgolang.org/x/text/language.Englishgo 1.26.6 MIT-0 · 2026-09-04
- golang.org/x/text v0.23.0: collate.New 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. HOWgolang.org/x/text/collate.Newgo 1.26.6 MIT-0 · 2026-09-04