CodeSampleX

Recordsgolanggithub.com/jackc/pgconn

there is a sample for this release and API (1)

Compatibility cube

Pick any two dimensions as axes; everything else becomes a filter. Clicking a cell pins its slice and drills one level deeper.

Fixed
Package versionv1.9.1-0.20210724152538-d89c8390a530 Symbolgithub.com/jackc/pgconn.ParseConfig
Filter Runtimego 1.26 Architecturex64 Execution contextgo libcglibc Clear filters
OS × Package manager
1 12026-10-10
How to read the grid

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

  • no sample at this coordinate yet
  • there is a sample here, and nothing of ours has run it at this coordinate yet
  • there is a sample here, and our run of it at this coordinate came back clean
  • there is a sample here, and our run of it at this coordinate failed
  • there is a sample here, and this coordinate records both a passing and a failing run of it
  • nothing recorded — unknown, never "works" and never "broken"
  • there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Cells are aggregates of everything still varying in this slice (the n/m count says how much). Click one to pin its coordinates and see the next level.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 5 · Steady 4

First observed break

v1.9.1-0.20210724152538-d89c8390a530

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:417d6d04e56086b25e3b9f0588126a7948b97a5a10a0fb3e12637291201b80b1

Library Version Health Measured there Projects
github.com/jackc/pgproto3/v2 v2.1.1 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
github.com/jackc/pgservicefile v0.0.0-20200714003250-2b9c44734f2b CANDIDATE Correlated change; unproven combination contract passed 11 project-days
github.com/stretchr/testify v1.7.0 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
golang.org/x/crypto v0.0.0-20210711020723-a769d52b0f97 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
golang.org/x/text v0.3.6 CANDIDATE Correlated change; unproven combination contract passed 11 project-days
github.com/jackc/chunkreader/v2 v2.0.1 PASS All observations passed contract passed 11 project-days
github.com/jackc/pgio v1.0.0 PASS All observations passed contract passed 11 project-days
github.com/jackc/pgmock v0.0.0-20210724152146-4ad1a8207f65 PASS All observations passed contract passed 11 project-days
github.com/jackc/pgpassfile v1.0.0 PASS All observations passed 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.

Moved: 5 · unchanged at every release: 4

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.