The nightly-rls workflow failed.
Run: https://github.com/webhook-co/webhook/actions/runs/32113774449
Classification: NON-TRANSIENT (a deterministic failure — not Neon latency).
Failure signature:
AssertionError: expected false to be true // Object.is equality
FAIL test/index-usage.test.ts
This suite runs the RLS / tenant-leak tests against the real Neon branch. Read the classification before assuming anything — there are four outcomes, and only one of them means a bug in the code under test:
NON-TRANSIENT — a deterministic failure. This one is a real bug.TRANSIENT — a timeout/connection error; the step already retried once.CONTENTION — something else touched the branch mid-run (roles are cluster-global and every run rotates their passwords). Not a bug in the code under test — re-run when the branch is idle.CANCELLED — the job was stopped (runtime cap, superseding run, or manual cancel).
The signature is scoped to vitest's failing-test output, so it should name the actual failure; if it says it was scraped from the whole log, the suite died before vitest reported and the lines are not known to come from a failing test. To have this investigated, comment @claude on this issue describing what to look at.
Prior failures: nightly-rls-failure issues.
The
nightly-rlsworkflow failed.Run: https://github.com/webhook-co/webhook/actions/runs/32113774449
Classification: NON-TRANSIENT (a deterministic failure — not Neon latency).
Failure signature:
This suite runs the RLS / tenant-leak tests against the real Neon branch. Read the classification before assuming anything — there are four outcomes, and only one of them means a bug in the code under test:
NON-TRANSIENT— a deterministic failure. This one is a real bug.TRANSIENT— a timeout/connection error; the step already retried once.CONTENTION— something else touched the branch mid-run (roles are cluster-global and every run rotates their passwords). Not a bug in the code under test — re-run when the branch is idle.CANCELLED— the job was stopped (runtime cap, superseding run, or manual cancel).The signature is scoped to vitest's failing-test output, so it should name the actual failure; if it says it was scraped from the whole log, the suite died before vitest reported and the lines are not known to come from a failing test. To have this investigated, comment
@claudeon this issue describing what to look at.Prior failures:
nightly-rls-failureissues.