You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[finding] The rest of the read-only data-command family exits 1 on a project with no database yet: migrate account-issuer, audit-metadata-bodies, meta --stored, secret orphans and rewrap, storage orphans read tables their boot deferred #21552
The cause is the one #21529 fixed for its three doors: the read-only boot defers the DDL, and the command's own first read hits a table the boot deferred.
Direction (the #21529 ruling 5965283666, applied to these doors; ⛔ not a ruling here)
If a read cannot be avoided, use isMissingTableError, only for the command's own deferred table. ⛔ Do not demote every refused read.
Also for triage (from the same report, a candidate)
Every read-only data-command boot of an absent database prints one [ObjectQLPlugin] sys_metadata_activation is registered but could not be read — packaged-ACTION enable/disable is UNAVAILABLE warning. PR #21093 (#20821) kept that line ON PURPOSE and recorded it as a false alarm on a dry run, so it may already be decided. Rule it in or out of this card.
Serial: this extends PR #21550's seam, so it starts once that PR lands.
Dedupe
MCP search_issues, repo-scoped, open and closed: 「read-only boot deferred table refused exit 1 secret orphans rewrap storage orphans absent database」 gave 6 hits.
Filing gate: ① a defect with a named position, a
findingof class (a).reach:was measured at a public door by the [finding] os migrate resume, recorded-by and value-shapes exit 1 on a project whose database does not exist yet, with an opaque "The database refused to run this query" from their own first read of a deferred table #21529 dev atb3f7cf99e4(CLI source unchanged since), on the same absent-database fixture with--json(os-dev report on [finding] os migrate resume, recorded-by and value-shapes exit 1 on a project whose database does not exist yet, with an opaque "The database refused to run this query" from their own first read of a deferred table #21529, out-of-scope finding 1; PR fix(cli,runtime): os migrate resume, recorded-by and value-shapes answer a project with no database yet with empty work #21550).domain:cliseat,session_016GiHYRmLSNWTfbX9gVQkpz. ⛔ Not a claim.packages/cli.os migrate planagainst a database that does not exist yet prints 6[sql-driver] DATABASE_ERROR … no such tablewarnings: the dry run defers the DDL, then its boot readssys_metadata,sys_metadata_activationandsys_migrationanyway #20821 (os migrate plan) and [finding] os migrate resume, recorded-by and value-shapes exit 1 on a project whose database does not exist yet, with an opaque "The database refused to run this query" from their own first read of a deferred table #21529 (resume,recorded-by,value-shapes), whose ruling named three doors only.What happens (measured, public door, a project whose database does not exist yet)
os migrate account-issueros migrate audit-metadata-bodiesfailures: 3(the audit, activity and metadata-audit tables)os migrate meta --storedos secret orphans/os secret rewrapscan_failed)os storage orphansfiles-to-references,summary-nulls,multi-value-columns,duplicatesThe cause is the one #21529 fixed for its three doors: the read-only boot defers the DDL, and the command's own first read hits a table the boot deferred.
Direction (the #21529 ruling
5965283666, applied to these doors; ⛔ not a ruling here)SchemaStack.tableAbsent(objectName)inpackages/cli/src/utils/schema-migrate.ts, true only for a table the deferred sync lists ascreate_table. These doors reuse it. ⛔ No second mechanism.isMissingTableError, only for the command's own deferred table. ⛔ Do not demote every refused read.Also for triage (from the same report, a candidate)
Every read-only data-command boot of an absent database prints one
[ObjectQLPlugin] sys_metadata_activation is registered but could not be read — packaged-ACTION enable/disable is UNAVAILABLEwarning. PR #21093 (#20821) kept that line ON PURPOSE and recorded it as a false alarm on a dry run, so it may already be decided. Rule it in or out of this card.Serial: this extends PR #21550's seam, so it starts once that PR lands.
Dedupe
MCP
search_issues, repo-scoped, open and closed: 「read-only boot deferred table refused exit 1 secret orphans rewrap storage orphans absent database」 gave 6 hits.os dev --database-driver memoryboots, then every data read answers 503 SERVICE_UNAVAILABLE — the package registry's CREATE TABLE sys_packages goes through driver-memory's no-op execute() #21492 (open) concerns the memory driver.single-posture deployment holding more than onesys_organizationrow boots silently — ADR-0131 §1.2(3) calls that precondition 「a refused boot」 and it is not; the harm surfaces five cards away (platform admin reads 0 rows on/data, system writes refused by #8844) #17010, [finding] the first boot of a new database prints[sql-driver] DATABASE_ERROR … no such table: sys_migrationon the warn channel: the engine's migration-gate read runs before the table is created #20768, external-datasource-federated-read: federated read returns empty — the external object→remote-table mapping never registers (boot ordering) #7737, [17.0.0-rc.0] os migrate apply: no occupancy/lock detection for SQLite, and boot-time DDL runs before the confirmation prompt #3917).Dedupe words: read-only boot deferred table refused exit 1; secret orphans rewrap absent database; storage orphans fresh project; meta stored account-issuer audit-metadata-bodies never-booted database.
Generated by Claude Code