Recordsgolanggithub.com/jackc/pgservicefilev0.0.0-20221227161230-091c0ba34f0apgservicefile.ReadServicefile
Change the conditions
Current conditions
pgservicefile.ReadServicefile @v0.0.0-20221227161230-091c0ba34f0alinux · 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 (2)
- Project observations
- nothing at this coordinate
- Contract verifications
- 1 / 1
- Last recorded
- 2026-08-27
Dependency Health
Observed combinations and failure evidence for this release
First observed break
v0.0.0-20221227161230-091c0ba34f0a
linux · go@1.26
3 FAIL · stage: PROJECT_PROCESS
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/stretchr/testify | v1.7.0 | CANDIDATE Correlated change; unproven combination | contract passed | 2 project-days |
| github.com/stretchr/testify | v1.8.1 | CANDIDATE Correlated change; unproven combination | contract passed | 11 project-days |
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.
| Library | v0.0.0-20240606120523-5a60cdf6a761 | v0.0.0-20221227161230-091c0ba34f0a | v0.0.0-20200714003250-2b9c44734f2b |
|---|---|---|---|
| github.com/stretchr/testify | v1.11.1 | v1.7.0 | v1.5.1 |
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.
Recent failure clusters
-
observed PROJECT_PROCESS Evidence gap ×3 v0.0.0-20221227161230-091c0ba34f0a → v0.0.0-20240606120523-5a60cdf6a761 os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.0.0-20221227161230-091c0ba34f0a os=linux · runtime=go@1.26 sha256:48312c939afd…# sample · <path> unknown field Host in struct literal of type pgx.ConnConfig · <path> unknown field Port in struct literal of type pgx.ConnConfig …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-30 · Last seen: 2026-08-30Diagnostic re-verification candidate