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
Complementary: #1186 adds a read-only Platform administration → Deployment diagnostics page (GET /api/platform/diagnostics) that reports exactly these three upgrades the installer cannot cover: the generated columns (run_telemetry.adapter / run_logs.level, with scripts/install-schema-extensions.sh as a copyable command), the run_artifacts.content column capacity vs the engine artifact limit, and Docker/browser runtime readiness. It does not change installer behavior — this issue's startup/upgrade checks would still be needed — but it gives operators a place to notice a missing script before the raw MySQL error surfaces.
Activity
fix(install): reapply schema extensions when upgrading
fix(install): reapply schema extensions when upgrading (#225)
cocofhu commentedon Nov 13, 2026
#225 已合入:
scripts/install-schema-extensions.sh在安装和./start.sh pull后补齐 001 的生成列并重放INSERT IGNOREseed(第 1 点),docs/deployment.md把migrations/分成三类(第 3 点)。第 2 点(自备 MySQL 启动时检查缺列并点名要执行的脚本 / 应用侧缺列友好报错)尚未完成,保持 open。gezerui888 commentedon Nov 15, 2026
I'd like to address the missing-column diagnostic for external MySQL telemetry queries. I'll open a focused PR shortly.
Robert0622 commentedon Nov 15, 2026
已对照当前 main 代码核实:
./start.sh pull时会补齐 001 的生成列并重放INSERT IGNOREseed;docs/deployment.md 已对 migrations/ 做分类说明。Error 1054 (42S22): Unknown column 'adapter')直接暴露给用户。看到 @gezerui888 已表示会为此提交聚焦 PR,期待该 PR;若短期内无进展,我们会将剩余范围记入 backlog 跟进。
Robert0622 commentedon Nov 15, 2026
开发状态更新(原帖第2点剩余范围:自备 MySQL 场景的启动期缺列检测与应用侧友好报错)
代码已完成并通过本地构建与测试,具体改动:
cmd/loopforge-schema-check:设置好AGENTFLOW_MYSQL_DSN后执行go run ./cmd/loopforge-schema-check,会查询information_schema.columns核对run_telemetry.adapter、run_logs.level等生成列是否存在;缺失时逐条列出table.column并给出可直接套用的mysql ... < migrations/001_run_obs_generated_columns.sql修复命令,非 0 退出,方便接入部署/启动脚本。internal/repo/runs.go:生成列缺失导致 MySQL 原始错误(Unknown column ...)时,不再把驱动错误原样抛给用户,改为包装成提示性的apperr.Unavailable错误,指向上面的检测命令和migrations/001_run_obs_generated_columns.sql/scripts/install-schema-extensions.sh。docs/deployment.md“Observability schema” 一节补充自备 MySQL 用户的检测步骤说明。go test ./internal/repo/...全部通过;Compose 安装/升级路径(PR [Loopforge 自动化] fix(install): reapply schema extensions when upgrading (refs #201) #225 已覆盖)未受影响。提交受阻:运行责任人账号对本仓库没有 GitHub push 权限(
remote: Permission to Tencent/LoopForge.git denied),PR 暂时无法发出。改动已保留在工作分支feature/fix-20261115-1015-7a51ae,待权限恢复后可直接推送发起 PR,无需重新开发。linus-liu-web commentedon Nov 21, 2026
Complementary: #1186 adds a read-only Platform administration → Deployment diagnostics page (
GET /api/platform/diagnostics) that reports exactly these three upgrades the installer cannot cover: the generated columns (run_telemetry.adapter/run_logs.level, withscripts/install-schema-extensions.shas a copyable command), therun_artifacts.contentcolumn capacity vs the engine artifact limit, and Docker/browser runtime readiness. It does not change installer behavior — this issue's startup/upgrade checks would still be needed — but it gives operators a place to notice a missing script before the raw MySQL error surfaces.feat(platform): add read-only deployment diagnostics page