Issues

TESTS.md section numbers collide on every pair of PRs that add a test file, and nothing catches it -- #996 one file over

#1024

· OffgridwithJD opened

on Sep 12, 2026

stripe_row_limit=1000 is below vector_length=1024, so FSST never applies and a text column stores at 1.95x

#1017

· jdatcmd opened

on Sep 12, 2026

Nothing runs orphan-scan, so the deleted-check half of the ledger comparison cannot fire -- and the blocker its docstring names was removed by #994/#998

#1015

· OffgridwithJD opened

on Sep 12, 2026

A mutation with two genuine targets cannot be recorded at all: --mutation refuses a multi-red run, so the only permitted merge writes no cause

#1014

· OffgridwithJD opened

on Sep 12, 2026

PGC_SEED does not seed the fuzzer: two runs with one seed share zero fixtures, because every generator call is a command substitution and bash re-seeds RANDOM in a subshell

#1011

· OffgridwithJD opened

on Sep 12, 2026

The ledger key omits the PostgreSQL major, so a check that exists on only some majors cannot be represented -- and orphan-scan will call it deleted

#1010

· OffgridwithJD opened

on Sep 12, 2026

The matrix summary prints a negative suite count: 248 accounted of 246 ran, so "-2 did not"

#1006

· OffgridwithJD opened

on Sep 12, 2026

The matrix report prints a negative count: 'of those, 248 accounted for their checks and -5 did not'

#999

· jdatcmd opened

on Sep 12, 2026

Every PR with a changelog entry inserts at the same anchor, so any two conflict for a reason unrelated to their changes

#996

· jdatcmd opened

on Sep 12, 2026

s3:// and gs:// absorb URL userinfo into the bucket name instead of refusing it, so the user is told the object does not exist

#995

· OffgridwithJD opened

on Sep 12, 2026

A collection-time vacuity refusal also reports the refused test as silently lost, so one bare skip produces two findings and only one is true

#991

· OffgridwithJD opened

on Sep 12, 2026

Two ledger rows name checks that no longer exist, so the census over-counts; nothing compares the ledger's keys against a run's

#983

· OffgridwithJD opened

on Sep 11, 2026

Navigation Menu

Uh oh!

All issues

TESTS.md section numbers collide on every pair of PRs that add a test file, and nothing catches it -- #996 one file over

stripe_row_limit=1000 is below vector_length=1024, so FSST never applies and a text column stores at 1.95x

Nothing runs orphan-scan, so the deleted-check half of the ledger comparison cannot fire -- and the blocker its docstring names was removed by #994/#998

A mutation with two genuine targets cannot be recorded at all: --mutation refuses a multi-red run, so the only permitted merge writes no cause

PGC_SEED does not seed the fuzzer: two runs with one seed share zero fixtures, because every generator call is a command substitution and bash re-seeds RANDOM in a subshell

The ledger key omits the PostgreSQL major, so a check that exists on only some majors cannot be represented -- and orphan-scan will call it deleted

The matrix summary prints a negative suite count: 248 accounted of 246 ran, so "-2 did not"

The matrix report prints a negative count: 'of those, 248 accounted for their checks and -5 did not'

Every PR with a changelog entry inserts at the same anchor, so any two conflict for a reason unrelated to their changes

s3:// and gs:// absorb URL userinfo into the bucket name instead of refusing it, so the user is told the object does not exist

A collection-time vacuity refusal also reports the refused test as silently lost, so one bare skip produces two findings and only one is true

Two ledger rows name checks that no longer exist, so the census over-counts; nothing compares the ledger's keys against a run's

Uh oh!

Search results