Recordsnpmpg8.23.0pg.Pool
Change the conditions
Current conditions
pg.Pool @8.23.0windows 11 · x64 · node 24 · npm 11 · node
0 of 58 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
- 158 / 177
- Contract verifications
- 0 / 58
- Independent reporting peers
- 1
- Last recorded
- 2026-09-14
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 3 ·
Steady 2
First observed break
8.23.0
linux · node@22.23 · moduleSystem=cjs · executionContext=node
11 FAIL
· stage: UNKNOWN
· fingerprint: sha256:9be950af9140edade9f2c5aa029896fb7dd194960195369ee277ef42a11d6868
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| pg-connection-string | 2.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| pg-pool | 3.14.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| pg-protocol | 1.16.0 | CANDIDATE Correlated change; unproven combination | contract passed | 14 project-days |
| pg-types | 2.2.0 | PASS All observations passed | contract passed | 14 project-days |
| pgpass | 1.0.5 | PASS All observations passed | contract passed | 14 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 | 8.23.0 | 8.16.3 |
|---|---|---|
| pg-connection-string | 2.14.0 | 2.9.1 |
| pg-pool | 3.14.0 | 3.10.1 |
| pg-protocol | 1.16.0 | 1.10.3 |
| pg-types | 2.2.0 | 2.2.0 |
| pgpass | 1.0.5 | 1.0.5 |
Moved: 3 · unchanged at every release: 2
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 UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×6 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:340c5f78ca35…Image hunterzo-egress-lab:local Building · Image hunterzo-egress-lab:local Built · Network hunterzo-egress-lab_fixture_net Creating …· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROCESS_START process start failed Evidence gap ×5 8.23.0 executionContext=node pg.Pool sha256:c12549970456…· structured-termination · gap diagnostic-missingEvidence quality: partial · Environment variants: 2 · First recorded: 2026-09-02 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 TS7034 ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:85a890982324…tests/crawl-budget.test.ts(<n>,<n>): error TS7034: Variable <str> implicitly has type <str> in some locations where its type cannot be determined.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS7005 ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:9157cca40f14…tests/crawl-budget.test.ts(<n>,<n>): error TS7005: Variable <str> implicitly has an <str> type.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_COMPILE exit 1 TS2349 ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:d6c915113d6a…src/crawl-policy.ts(<n>,<n>): error TS2349: This expression is not callable.typescript/tsc · compiler-diagnostic · outer npm runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed PROJECT_TEST exit 1 ERR_ASSERTION ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:53a7d182a4ae…AssertionError [ERR_ASSERTION]: The expression evaluated to a falsy value: · assert.ok(second.delayMs>0&&second.delayMs<=3000) …javascript/test-runner · test-runner-diagnostic · outer npm testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13
-
observed UNKNOWN exit 1 Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:09a269b7ef7e…Traceback (most recent call last): · File <str>, line 55, in <module> · assert after[name]>before[name],name+<str> · ^^^^^^^^^^^^^^^^^^^^^^^^· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:2d74008e28fc…broker-1 | CID: 29, · broker-1 | JSON: 114, · broker-1 | XML: 142, · broker-1 | PG_NODE_TREE: 194,· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:5da6f88d33d6…> hunterzo@0.1.0 test:e2e · > playwright test · Running 3 tests using 1 worker …npm · unclassified-diagnostic · outer npm run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERR_ASSERTION Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:96a74317c075…✔ parallel preparation shares cache and preserves original observation hashes (82.3113ms) …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 ERROR Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:c19eb88451fd…✖ parallel preparation shares cache and preserves original observation hashes (68.6352ms) …node · unclassified-diagnostic · outer node · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×3 8.23.0 executionContext=node · moduleSystem=esm · os=windows · runtime=node@24.13 pg.Pool sha256:535b814ac7ea…time=<str> level=warning msg=<str> · ai Built · Container hunterzo-ai-1 Recreate · Container hunterzo-ai-1 Recreated· unclassified-diagnostic · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-13 · Last seen: 2026-09-13Diagnostic re-verification candidate
Showing the 12 most-reported of 32 recorded failure clusters. The rest are single reports.