root/geo
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: complete Phase 69 of generated-code drift diagnosis and update task plan status

Browse Source
This commit is contained in:
liangxu
2026-07-15 00:04:24 +08:00
parent 3037cfe059
commit 6adcec4849
3 changed files with 10 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
findings.md
+2
View File
@@ -18,6 +18,8 @@
- `generated/models.go` currently has no local diff before regeneration; `MediaSupplyOrder` fields are aligned by the committed generator output.
- Gitea Backend CI pins `sqlc v1.30.0`, matching the local binary exactly, then runs `make sqlc-generate` and `git diff --exit-code -- server/internal/tenant/repository/generated`.
- Version-mismatch hypothesis is falsified. The next deterministic probe is the exact CI generation command.
- Exact CI generation reproduces a one-file diff: `generated/models.go` gains 26 lines for `MediaSupplyFavoriteGroup`, `MediaSupplyFavoriteOwner`, and `MediaSupplyFavoriteResource` immediately before `MediaSupplyOrder`.
- Root cause: the schema already contains the three media-supply favorite tables, but their generated sqlc model structs were not committed. The reported `MediaSupplyOrder` line is only the diff insertion boundary.
- The reported `MediaSupplyOrder` is generated in `server/internal/tenant/repository/generated/models.go` around line 699.
- Screenshot evidence: on client `e83077a0...`, `monitoring_collect:7995` for Doubao failed with `doubao_challenge_required`, while later Doubao task `monitoring_collect:7989` also appeared as failed with the same message.
- Screenshot refinement: the first challenged desktop task `#7224` shows attempt 1, while later `monitoring_collect:7989` shows attempt 0 and the same copied challenge message. This indicates the later task was bulk-terminalized without adapter execution, but recorded as `failed`, making cancellation look like another failed attempt.