The files deployment failed on this: relation "clearance_revocations" does not exist. A policy body is parsed when the policy is CREATED, under
whatever search_path the migration runs with — and the migrator's does not
include the tenant schema. So SELECT 1 FROM clearance_revocations inside
a policy is a script that parses perfectly, passes every test this repository
had, and fails only against a real database.
Four references across 004 and 005, all now :schema.-qualified, which is the
convention 003 already followed.
⚠️ It failed AFTER creating the table, so t_default was left with
clearance_revocations present and the migration unrecorded. Both scripts use
CREATE TABLE IF NOT EXISTS and DROP POLICY IF EXISTS — the idempotence the
migrator's own documentation asks for — so re-running lands cleanly on that
state rather than needing it unpicked by hand.
The new test would have caught it: reintroducing the exact line fails with
the file and line number. It skips IS DISTINCT FROM and EXTRACT(x FROM y), which are not table references and which the first version of the check
reported as bugs.
accounts.flamenet.io is already on the new image and healthy; files is still
on the previous one because the migration gate stopped before it was
restarted, which is the gate working.
The files deployment failed on this: `relation "clearance_revocations"
does not exist`. A policy body is parsed when the policy is CREATED, under
whatever search_path the migration runs with — and the migrator's does not
include the tenant schema. So `SELECT 1 FROM clearance_revocations` inside
a policy is a script that parses perfectly, passes every test this repository
had, and fails only against a real database.
Four references across 004 and 005, all now :schema.-qualified, which is the
convention 003 already followed.
⚠️ It failed AFTER creating the table, so t_default was left with
clearance_revocations present and the migration unrecorded. Both scripts use
CREATE TABLE IF NOT EXISTS and DROP POLICY IF EXISTS — the idempotence the
migrator's own documentation asks for — so re-running lands cleanly on that
state rather than needing it unpicked by hand.
The new test would have caught it: reintroducing the exact line fails with
the file and line number. It skips `IS DISTINCT FROM` and `EXTRACT(x FROM
y)`, which are not table references and which the first version of the check
reported as bugs.
accounts.flamenet.io is already on the new image and healthy; files is still
on the previous one because the migration gate stopped before it was
restarted, which is the gate working.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The files deployment failed on this:
relation "clearance_revocations" does not exist. A policy body is parsed when the policy is CREATED, underwhatever search_path the migration runs with — and the migrator's does not
include the tenant schema. So
SELECT 1 FROM clearance_revocationsinsidea policy is a script that parses perfectly, passes every test this repository
had, and fails only against a real database.
Four references across 004 and 005, all now :schema.-qualified, which is the
convention 003 already followed.
⚠️ It failed AFTER creating the table, so t_default was left with
clearance_revocations present and the migration unrecorded. Both scripts use
CREATE TABLE IF NOT EXISTS and DROP POLICY IF EXISTS — the idempotence the
migrator's own documentation asks for — so re-running lands cleanly on that
state rather than needing it unpicked by hand.
The new test would have caught it: reintroducing the exact line fails with
the file and line number. It skips
IS DISTINCT FROMandEXTRACT(x FROM y), which are not table references and which the first version of the checkreported as bugs.
accounts.flamenet.io is already on the new image and healthy; files is still
on the previous one because the migration gate stopped before it was
restarted, which is the gate working.
assigned to @paulhitt
mentioned in commit
a3393f1fe4