CodeSampleX

Recordsgolanggithub.com/spf13/castv1.4.1cast.ToDurationE

Change the conditions
Fixed
OSlinux Package versionv1.4.1 Symbolcast.ToDurationE
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcmusl Clear filters

Current conditions

cast.ToDurationE @v1.4.1linux · musl · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-28
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.4.1

linux · go@1.26

1 FAIL · stage: PROJECT_TEST · fingerprint: sha256:ed0d65a0d993a5e94e1d251ec22ca8c79ab1911490fae7d47428b99a68761db5

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.2.2 CANDIDATE Correlated change; unproven combination nothing measured 3 project-days
github.com/stretchr/testify v1.9.0 CANDIDATE Correlated change; unproven combination contract passed 1 project-day

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.10.0v1.7.0v1.4.1v1.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.

Recent failure clusters