Recordsgolanggo.uber.org/goleak
Change the conditions
Current conditions
go.uber.org/goleak.VerifyNone @v1.3.0glibc · x64 · go 1.26 · 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
- 3 / 3
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-03
Exact records
This slice is down to its measured combinations — the environments below are exactly what ran.
-
debian glibc · x64 · go 1.26 · go · go
1 of 1 passed
Verified — this network ran a contract at this coordinate.
-
ubuntu glibc · x64 · go 1.26 · go 1
3 of 3 passed
Observed — real project builds reported from this coordinate.
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v1.3.0
linux · go@1.26
1 FAIL
· stage: PROJECT_TEST
· fingerprint: sha256:2b1cd55a358000c17d483656568fc2dee859d7d129e76ec841f2159b73497c1c
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.3.0 | v1.2.0 |
|---|---|---|
| github.com/stretchr/testify | v1.8.1 | v1.8.1 |
Moved: 0 · 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.