CodeSampleX

Recordsgolanggithub.com/spf13/castfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

contract failure: CoerceStringSlice([]int{10, 20}) failed · exit status 1

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-27 · Last seen: 2026-10-27

sha256:8b8ad691ca7f…

github.com/spf13/cast.ToBool github.com/spf13/cast.ToBoolE github.com/spf13/cast.ToDuration github.com/spf13/cast.ToDurationE github.com/spf13/cast.ToFloat64 github.com/spf13/cast.ToFloat64E github.com/spf13/cast.ToInt github.com/spf13/cast.ToInt64 github.com/spf13/cast.ToInt64E 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 github.com/spf13/cast.ToTime github.com/spf13/cast.ToTimeE

Where it was measured

PASS means the release recorded a passing observation at UNKNOWN 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

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.

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.

Libraryv1.7.0v1.4.1v1.3.1v1.3.0
github.com/stretchr/testify — v1.9.0 v1.2.2 v1.2.2
github.com/frankban/quicktest 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

Published answers for the affected releases

Back to the package