在前后端开发联调前 的提交20260223

This commit is contained in:
Neo
2026-02-23 23:02:20 +08:00
parent 254ccb1e77
commit fafc95e64c
1142 changed files with 10366960 additions and 36957 deletions

View File

@@ -0,0 +1,150 @@
- [P20260221-203657] 2026-02-21 20:36:57 +0800
- summary: CONTEXT TRANSFER: We are continuing a conversation that had gotten too long. Here is a summary: --- ## TASK 1: 前后端联调 — a…
- prompt:
```text
CONTEXT TRANSFER: We are continuing a conversation that had gotten too long. Here is a summary:
---
## TASK 1: 前后端联调 — admin-web 任务配置、提交、执行、验证
**STATUS**: in-progress
**USER QUERIES**: All queries in this conversation are continuations of the same task from previous context transfers.
**SHORT DESCRIPTION**: 前后端联调:通过 admin-web 浏览器配置 ETL 任务api_full, full_window, 2025-11-01~2026-02-20, 30天窗口切分, force-full, 31个任务提交执行修复发现的 BUG做回归测试和数据检验输出详细文档。
**DETAILS**:
### 执行历史
#### 第一次执行(已完成)
- execution_id: `dbf0c29a-253a-4705-a1ef-35cd71243d48`
- 结果: 10 成功, 31 失败, 耗时 590.7s
- 根因: `DWS_ASSISTANT_DAILY` SQL 字段引用错误 → 已修复 4 处改动
- 文档: `export/SYSTEM/LOGS/2026-02-21__etl_run_result.md`, `export/SYSTEM/LOGS/2026-02-21__dws_assistant_daily_bug_fix.md`
#### 第二次执行(已完成)
- execution_id: `e21e1935-5abf-434f-9984-69c492402db7`
- 结果: 耗时 150.4s, 31 个任务
- `DWS_ASSISTANT_DAILY` ✅, `DWS_ASSISTANT_MONTHLY` ❌ UniqueViolation, `DWS_ASSISTANT_CUSTOMER` ❌ UndefinedColumn site_id
- 文档: `export/SYSTEM/LOGS/2026-02-21__etl_run_result_v2.md`
#### 第三次执行(已完成)
- execution_id: `abc94b2d-615f-42ea-83cc-ce687524a6ea`
- 结果: 耗时 681.2s, 9 成功, 22 失败
- BUG 1/2/3 全部修复验证通过
- 新发现 BUG 4: `DWS_MEMBER_CONSUMPTION` 的 `dim_member.site_id` 不存在
- 文档: `export/SYSTEM/LOGS/2026-02-21__etl_run_result_v3.md`, `export/SYSTEM/LOGS/2026-02-21__etl_run_raw_v3.json`
#### 第四次执行(已完成)
- execution_id: `efd4f421-ee10-4244-833f-7b2d68c3c05b`
- 结果: 耗时 11m55s, 10 成功, 21 失败
- BUG 4 修复验证通过(`DWS_MEMBER_CONSUMPTION` ✅)
- 新发现 BUG 5: `DWS_MEMBER_VISIT` → `UndefinedColumn: birthday` (dim_member 无此字段)
- 文档: `export/SYSTEM/LOGS/2026-02-21__etl_run_result_v4.md`, `export/SYSTEM/LOGS/2026-02-21__etl_run_raw_v4.json`
#### 第五次执行(已完成,需分析)
- execution_id: `fe87144a-687d-4ce0-9b79-6bd0186b2be3`
- 结果: 耗时 11m37s (20:19:52 ~ 20:31:29), exit_code=0
- BUG 5 的 `birthday` 修复已部署,但出现新的 BUG 6
- 新发现 BUG 6: `DWS_MEMBER_VISIT` → `UndefinedColumn: site_table_id` 不存在(在 `_extract_table_info` 方法中)
- 级联导致后续 20 个任务全部 InFailedSqlTransaction 失败
- 原始日志: `export/SYSTEM/LOGS/2026-02-21__etl_run_raw_v5.json`
- **尚未导出 v5 结果报告**
### 已修复的 BUG 汇总
**BUG 1** (第一次发现,第二次验证通过):
- 文件: `apps/etl/connectors/feiqiu/tasks/dws/assistant_daily_task.py`4 处改动
**BUG 2** (第二次发现,第三次验证通过):
- 文件: `apps/etl/connectors/feiqiu/tasks/dws/assistant_monthly_task.py`
- GROUP BY 去掉 nickname/level 维度字段,改用 `MAX()` 聚合
**BUG 3** (第二次发现,第三次验证通过):
- 文件: `apps/etl/connectors/feiqiu/tasks/dws/assistant_customer_task.py`
- `dim_member` 表 `WHERE site_id` → `WHERE register_site_id`
**BUG 4** (第三次发现,第四次验证通过):
- 根因: `dwd.dim_member` 和 `dwd.dim_member_card_account` 表没有 `site_id` 字段,只有 `register_site_id`
- 修复了 4 处(全部 `site_id` → `register_site_id`
1. `member_consumption_task.py` — `_extract_member_info`
2. `member_consumption_task.py` — `_extract_card_balances`
3. `member_visit_task.py` — `_extract_member_info`
4. `finance_recharge_task.py` — `_extract_card_balances`
**BUG 5** (第四次发现,第五次已部署但被 BUG 6 遮蔽):
- 文件: `apps/etl/connectors/feiqiu/tasks/dws/member_visit_task.py`
- `_extract_member_info` SQL 移除 `birthday` 字段dim_member 无此字段)
- transform 中 `member_birthday` 改为 `None`
- 已添加 CHANGE 注释
### 待修复 BUG 6当前阻塞项
- 任务: `DWS_MEMBER_VISIT`
- 错误: `UndefinedColumn: 字段 "site_table_id" 不存在` (LINE 3: site_table_id AS table_id)
- 位置: `member_visit_task.py` → `_extract_table_info()` line ~334
- 根因: SQL 查询某个表时引用了 `site_table_id` 字段,但该字段不存在
- 需要查看 `_extract_table_info` 方法的 SQL确认正确的字段名
### 认证信息
- refresh_token7 天有效,到 2026-02-28: `eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxIiwic2l0ZV9pZCI6Mjc5MDY4NTQxNTQ0MzI2OSwidHlwZSI6InJlZnJlc2giLCJleHAiOjE3NzIyNjM0NjN9.XYoda5lfxNtTSAGWoLlYhS9cA-hTK9iqK0SqUyn2KV4`
- 刷新 API: `POST http://localhost:8000/api/auth/refresh` body: `{"refresh_token": "..."}`
- 提交执行 API: `POST http://localhost:8000/api/execution/run`(注意不是 `/submit`
- token 文件: `scripts/ops/.monitor_token`
**NEXT STEPS**:
1. **修复 BUG 6** — 读取 `member_visit_task.py` 的 `_extract_table_info` 方法,找到 `site_table_id` 引用,查 DDL 确认正确字段名并修复
2. **导出 v5 结果报告** — 到 `export/SYSTEM/LOGS/2026-02-21__etl_run_result_v5.md`
3. **提交第六次执行** — 验证 BUG 5+6 修复
4. **如果仍有失败** — 继续修复
5. **如果全部成功** — 导出最终 BUG 修复汇总报告
6. **运行 /audit** — 多个 `tasks/` 文件的修改命中高风险路径,需要审计
**FILEPATHS**:
- `apps/etl/connectors/feiqiu/tasks/dws/member_visit_task.py` — BUG 5 已修复BUG 6 待修复
- `apps/etl/connectors/feiqiu/tasks/dws/assistant_daily_task.py` — BUG 1 已修复
- `apps/etl/connectors/feiqiu/tasks/dws/assistant_monthly_task.py` — BUG 2 已修复
- `apps/etl/connectors/feiqiu/tasks/dws/assistant_customer_task.py` — BUG 3 已修复
- `apps/etl/connectors/feiqiu/tasks/dws/member_consumption_task.py` — BUG 4 已修复
- `apps/etl/connectors/feiqiu/tasks/dws/finance_recharge_task.py` — BUG 4 已修复
- `db/etl_feiqiu/schemas/dwd.sql` — dim_member DDL 参考
- `db/etl_feiqiu/schemas/dws.sql` — DWS 表 DDL 参考
- `scripts/ops/resubmit_v5.py` — 提交脚本模板(正确的 API payload 格式)
- `scripts/ops/poll_v5.py` — 轮询脚本模板
- `export/SYSTEM/LOGS/2026-02-21__etl_run_raw_v5.json` — 第五次执行原始日志
**USER CORRECTIONS AND INSTRUCTIONS**:
- 所有说明性文字使用简体中文
- 输出路径必须通过 `_env_paths.get_output_path()` 从 `.env` 读取,禁止硬编码
- `scripts/ops/` 下的脚本必须 `load_dotenv` 加载根 `.env`
- 提交执行 API 路径是 `/api/execution/run`(不是 `/submit`
- 提交 payload 格式参考 `resubmit_v4.py`(包含 tasks 列表、flow、processing_mode 等字段)
- 改动命中 `tasks/` 高风险路径,完成后需要运行 `/audit`
- 后端服务运行在 `localhost:8000`admin-web 通过 pnpm dev 运行(进程 6
Files to read:
- `apps/etl/connectors/feiqiu/tasks/dws/member_visit_task.py`
- `db/etl_feiqiu/schemas/dwd.sql`
- `db/etl_feiqiu/schemas/dws.sql`
- `scripts/ops/resubmit_v5.py`
- `scripts/ops/poll_v5.py`
- `export/SYSTEM/LOGS/2026-02-21__etl_run_raw_v5.json`
USER QUERIES(most recent first):
1. Output:
Command executed successfully with no output.
Exit Code: 0
2. Output:
Command executed successfully with no output.
Exit Code: 0
---
METADATA:
The previous conversation had 2 messages.
INSTRUCTIONS:
Continue working until the user query has been fully addressed. Do not ask for clarification - proceed with the work based on the context provided.
IMPORTANT: you need to read from the files to Read section
```