Recordsgolanggolang.org/x/textfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×7
<path> <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run, go test · First recorded: 2026-08-30 · Last seen: 2026-10-11
sha256:964ddac6b19a…
golang.org/x/text/encoding.HTMLEscapeUnsupported golang.org/x/text/encoding.Replacement golang.org/x/text/encoding/charmap.CodePage437 golang.org/x/text/encoding/charmap.ISO8859_1 golang.org/x/text/transform.ErrShortDst
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.
- v0.43.0 PASS 6 passing observations
- v0.42.0 FAIL
- v0.41.0 PASS 7 passing observations
- v0.35.0 FAIL
- v0.34.0 PASS 2 passing observations
- v0.33.0 FAIL
- v0.29.0 FAIL
- v0.13.0 FAIL
- v0.3.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×7 2026-08-30 → 2026-10-11
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 failing release v0.3.0 → first passing release v0.3.2
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last passing release v0.3.8 → first failing release v0.13.0
Releases between them never measured at this stage: 5
What differs across the boundary
- golang.org/x/tools v0.1.12 → v0.14.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.13.0 → first passing release v0.14.0
What differs across the boundary
- golang.org/x/tools v0.6.0 → v0.14.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 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.30.0
What differs across the boundary
- golang.org/x/tools v0.37.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.31.0 → first failing release v0.33.0
Releases between them never measured at this stage: 1
What differs across the boundary
- golang.org/x/tools v0.38.0 → v0.40.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.33.0 → first passing release v0.34.0
What differs across the boundary
- golang.org/x/tools v0.41.0 → v0.40.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 passing release v0.34.0 → first failing release v0.35.0
What differs across the boundary
- golang.org/x/tools v0.41.0 → v0.42.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.35.0 → first passing release v0.41.0
Releases between them never measured at this stage: 4
What differs across the boundary
- golang.org/x/tools v0.48.0 → v0.42.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.41.0 → first failing release v0.42.0
What differs across the boundary
- golang.org/x/tools v0.48.0 → v0.49.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.42.0 → first passing release v0.43.0
What differs across the boundary
- golang.org/x/tools v0.51.0 → v0.49.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.43.0 | v0.42.0 | v0.41.0 | v0.35.0 | v0.34.0 | v0.33.0 | v0.29.0 | v0.13.0 |
|---|---|---|---|---|---|---|---|---|
| golang.org/x/tools | v0.51.0 | v0.49.0 | v0.48.0 | v0.42.0 | v0.41.0 | v0.41.0 | v0.36.0 | v0.14.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
- No resolved dependency tree for v0.3.2 or for v0.3.0, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/text v0.42.0: encoding.Encoder 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/encoding.Encodergo 1.26.6 MIT-0 · 2026-09-15
- golang.org/x/text v0.42.0: transform.ErrShortDst 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/transform.ErrShortDst MIT-0 · 2026-09-15
- golang.org/x/text v0.42.0: encoding.Replacement 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/encoding.Replacement MIT-0 · 2026-09-15
- golang.org/x/text v0.33.0: charmap.CodePage437 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/encoding/charmap.CodePage437go 1.26.6 MIT-0 · 2026-10-11
- golang.org/x/text v0.33.0: japanese.ShiftJIS 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/encoding/japanese.ShiftJISgo 1.26.6 MIT-0 · 2026-10-11
- golang.org/x/text v0.33.0: encoding.Nop 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/encoding.Nopgo 1.26.6 MIT-0 · 2026-10-11