Recordsgolanggithub.com/jackc/pgpassfilefailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestIntegrationChangedSinceSeesOutOfBandStatusChanges (1.49s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-27 · Last seen: 2026-08-27
sha256:7e738c976c51…
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.
- v1.0.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-27 → 2026-08-27
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.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/jackc/pgpassfile v1.0.0: Demonstrate that ParsePassfile silently drops lines with unescaped colons in fields and requires backslash escaping for literal colons and backslashes. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpgpassfile.ParsePassfilepgpassfile.FindPasswordpgpassfile.ReadPassfilego MIT-0 · 2026-08-19
- github.com/jackc/pgpassfile v1.0.0: parse pgpass file and find password This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWpgpassfile.FindPasswordpgpassfile.ParsePassfile MIT-0 · 2026-08-18