CodeSampleX

Recordsgolanggithub.com/jackc/pgx/v4v4.0.0-pre1.0.20190824185557-6972a5742186github.com/jackc/pgx/v4.LogLevelInfo

Change the conditions
Fixed
Symbolgithub.com/jackc/pgx/v4.LogLevelInfo Package managergo 1
Filter OSubuntu glibc Runtimego 1.26 Package versionv4.0.0-pre1.0.20190824185557-6972a5742186 Architecturex64 libcglibc Clear filters

Current conditions

github.com/jackc/pgx/v4.LogLevelInfo @v4.0.0-pre1.0.20190824185557-6972a5742186ubuntu glibc · x64 · go 1.26 · go 1

0 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 failed (1)

Project observations
6 / 6
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-10-15

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 12 · Unknown 3 · Steady 5

First observed break

v4.0.0-pre1.0.20190824185557-6972a5742186

linux · go@1.26

2 FAIL · stage: PROJECT_RESOLVE · fingerprint: sha256:63ec90bf15b4853135a4e32c950cb5a982d5d71f3c7697e0d5f4d57f08523098

Library Version Health Measured there Projects
github.com/jackc/pgconn v0.0.0-20190824142844-760dd75542eb CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/jackc/pgconn v1.9.0 CANDIDATE Correlated change; unproven combination builds observed 3 project-days
github.com/jackc/pgconn v1.9.1-0.20210724152538-d89c8390a530 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/jackc/pgproto3/v2 v2.0.0-alpha1.0.20190609003834-432c2951c711 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/jackc/pgproto3/v2 v2.1.1 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
github.com/jackc/pgtype v0.0.0-20190824184912-ab885b375b90 CANDIDATE Correlated change; unproven combination contract passed 3 project-days
github.com/jackc/pgtype v0.0.0-20190828014616-a8802b16cc59 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
github.com/jackc/puddle v0.0.0-20190608224051-11cab39313c9 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
github.com/shopspring/decimal v0.0.0-20180709203117-cd690d0c9e24 CANDIDATE Correlated change; unproven combination nothing measured 11 project-days
github.com/stretchr/testify v1.4.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/stretchr/testify v1.7.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
go.uber.org/zap v1.10.0 CANDIDATE Correlated change; unproven combination nothing measured 9 project-days
github.com/cockroachdb/apd v1.1.0 UNKNOWN No linked outcome measured nothing measured 11 project-days
github.com/satori/go.uuid v1.2.0 UNKNOWN No linked outcome measured nothing measured 11 project-days
gopkg.in/inconshreveable/log15.v2 v2.0.0-20180818164646-67afb5ed74ec UNKNOWN No linked outcome measured nothing measured 9 project-days
github.com/jackc/pgio v1.0.0 PASS All observations passed contract passed 11 project-days
github.com/rs/zerolog v1.15.0 PASS All observations passed contract passed 11 project-days
github.com/sirupsen/logrus v1.4.2 PASS All observations passed contract passed 10 project-days
golang.org/x/xerrors v0.0.0-20190717185122-a985d3407aa7 PASS All observations passed contract passed 5 project-days
golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1 PASS All observations passed contract passed 6 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.

Moved: 7 · unchanged at every release: 10

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