From ab12fea4745cf22fb7648c1c25b18433ac8a3650 Mon Sep 17 00:00:00 2001 From: weichen Date: Thu, 15 Oct 2026 14:04:03 +0000 Subject: [PATCH] Register exec env tables in storage migration Why: Schema 35 adds exec_env_requests and exec_env_bindings. The SQLite-to-Postgres copier refuses to run when a business table is missing from its ordered list. Evidence: SELF go test ./cmd/storage-migrate -run TestCopyOrderCoversAllFixtureTables. CI run 3343 failed on this exact check. Impact: Those two tables move with the rest of the database. They have no foreign keys, so they can follow the existing recovery tables. Refs: pull 206 Co-authored-by: Cursor --- cmd/storage-migrate/main.go | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cmd/storage-migrate/main.go b/cmd/storage-migrate/main.go index 84543fc..d1a8521 100644 --- a/cmd/storage-migrate/main.go +++ b/cmd/storage-migrate/main.go @@ -298,6 +298,8 @@ var copyOrder = []string{ "account_events", "redeem_attempts", "recovery_proposals", "recovery_proposal_proofs", + // v35 分层 Python 环境（无外键；申请与会话绑定要随库迁走） + "exec_env_requests", "exec_env_bindings", } const controlDDL = `