topfans/docker
zerosaturation 89d5d12450 fix(task): backfill id=1/2 trigger_event + cleanup misleading NULL comments
daily_browse_asset (id=2) / daily_login (id=1) 之前永远不触发,根因:
2026_07_21_004 迁移只 backfill 了 id=3/4 的 trigger_event=task_key,
id=1/2 留 NULL。但 ProcessTaskEvent 引擎按 trigger_event = ? 严格匹配
(spec §4 单一隔离单元),NULL 不会命中,前端 reportEvent 后引擎跑空
循环、daily-tasks 任务永远 pending。

修复:
- 新增 2026_07_27_005 迁移:回填 id=1/2 的 trigger_event=task_key(幂等)
- 修订原 004 迁移的错误注释('trigger_event 留 NULL'误导后人)
- model/task_models.go:删除 'NULL 仍走 def.TaskKey 兜底' 不实承诺
- impl plan §37/39:修订错描述('暂不依赖 trigger_event 列')
- docker/init-db.sql:124668/124671:重建 dev DB 时也带 trigger_event
- daily_task_repo_test.go:补 2 个回归测试
  - NullTriggerEvent_NotMatched:trigger_event=NULL 时查不到
  - TriggerEventEqualsTaskKey_Matches:trigger_event=task_key 时能命中

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-07-27 16:36:40 +08:00
..
sql/migrations
.env
.env.local
.env.prod feat:修改周边验证 2026-07-17 16:53:57 +08:00
build.sh fix(deploy): health probe paths + starbookService deployment removal (config 4.3) 2026-07-24 14:04:41 +08:00
cleanup-logs.sh
deploy.sh fix(deploy): health probe paths + starbookService deployment removal (config 4.3) 2026-07-24 14:04:41 +08:00
dify-deploy.sh feat:去掉无用的函数方法 2026-07-09 16:08:25 +08:00
docker-compose.local.yml fix(deploy): health probe paths + starbookService deployment removal (config 4.3) 2026-07-24 14:04:41 +08:00
docker-compose.prod.yml fix(deploy): health probe paths + starbookService deployment removal (config 4.3) 2026-07-24 14:04:41 +08:00
Dockerfile.services fix(deploy): health probe paths + starbookService deployment removal (config 4.3) 2026-07-24 14:04:41 +08:00
init-db.sql fix(task): backfill id=1/2 trigger_event + cleanup misleading NULL comments 2026-07-27 16:36:40 +08:00
SCHEMA_DIFF_REPORT.txt
start.sh
快速配置更新指南.md