Recordsgolanggithub.com/spf13/castfailure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-21 · Last seen: 2026-08-21
github.com/spf13/cast.ToBool github.com/spf13/cast.ToBoolE github.com/spf13/cast.ToDuration github.com/spf13/cast.ToDurationE github.com/spf13/cast.ToInt github.com/spf13/cast.ToIntE github.com/spf13/cast.ToString github.com/spf13/cast.ToStringE github.com/spf13/cast.ToStringMapString github.com/spf13/cast.ToStringMapStringE github.com/spf13/cast.ToStringSlice github.com/spf13/cast.ToStringSliceE
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.
- v1.10.0 PASS 13 passing observations
- v1.7.0 FAIL
- v1.4.1 PASS 7 passing observations
- v1.3.1 PASS 6 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-21 → 2026-08-21
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.4.1 → first failing release v1.7.0
What differs across the boundary
- github.com/frankban/quicktest — → v1.14.6 hypothesis
- github.com/stretchr/testify v1.2.2, v1.9.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 v1.7.0 → first passing release v1.10.0
Both trees resolved every dependency to the same version. Nothing here moved.
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 | v1.10.0 | v1.7.0 | v1.4.1 | v1.3.1 |
|---|---|---|---|---|
| github.com/stretchr/testify | — | — | v1.9.0 | v1.2.2 |
| github.com/frankban/quicktest | v1.14.6 | v1.14.6 | — | — |
Moved: 1 · unchanged at every release: 1
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
- github.com/spf13/cast v1.7.0: ToBool 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. HOWgithub.com/spf13/cast.ToBool MIT-0 · 2026-08-21
- github.com/spf13/cast v1.7.0: ToString, ToStringE, ToInt 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. HOWcast.ToStringcast.ToStringEcast.ToIntcast.ToIntEcast.ToBoolcast.ToBoolEcast.ToDurationcast.ToDurationEcast.ToStringSlicecast.ToStringSliceEcast.ToStringMapStringcast.ToStringMapStringE MIT-0 · 2026-08-21