CodeSampleX

Recordsgolanggithub.com/jackc/pgtypefailure issue

Failure signature

PROJECT_TEST Evidence gap ×2

Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-07 · Last seen: 2026-09-07

github.com/jackc/pgtype.ConnInfo.InitializeDataTypes github.com/jackc/pgtype.Int4.AssignTo github.com/jackc/pgtype.Int4.Set github.com/jackc/pgtype.Int8 github.com/jackc/pgtype.Int8.AssignTo github.com/jackc/pgtype.Int8.Set github.com/jackc/pgtype.JSONB.AssignTo github.com/jackc/pgtype.JSONB.Set github.com/jackc/pgtype.NewConnInfo github.com/jackc/pgtype.Present github.com/jackc/pgtype.Text.AssignTo github.com/jackc/pgtype.Text.DecodeBinary github.com/jackc/pgtype.Text.DecodeText github.com/jackc/pgtype.Text.EncodeBinary github.com/jackc/pgtype.Text.EncodeText github.com/jackc/pgtype.Text.Set

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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: 4 · unchanged at every release: 5

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.

Evidence gaps

Published answers for the affected releases

Back to the package