myxce/.wolf/bugs/bug-1966.md
Rongsong Shen c71049f28d
docs(buglog): record Gitea sync for bug-1958..bug-1966
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
2026-10-10 10:20:18 +00:00

2.1 KiB

id status status_updated status_note component severity timestamp last_seen occurrences files tags related gitea_issue gitea_synced_status gitea_synced_hash
bug-1966 open 2026-10-10 newly logged apiserver noise 2026-10-10T10:16:16Z 2026-10-10T10:16:16Z 1
src/frontend/apiserver/controllers/hosts.go
src/frontend/apiserver/docs/swagger.yaml
apiserver
docs
swagger
397 open d98430bca460

bug-1966: apiserver swagger generation fails on hosts.go models.Error; published swagger is a stale stub

Description

Observed: (source reading; follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)) swag init -g cmd/main.go fails: ParseComment error in controllers/hosts.go for comment: '// @Failure 400 {object} models.Error': cannot find type definition: models.Error. docs/swagger.yaml is a 212-line stub last generated before the meson merge (no job-control endpoints).

Expected: Swagger generates from the annotations and the published spec covers the API. Impact: API documentation missing/stale. Found by: follow-up of the 2026-10-10 P0 fixes (bug-1936..1957)

Environment

  • OS: no /etc/os-release; Docker container; NixOS kernel; kernel Linux 6.18.33 x86_64
  • libc: glibc 2.42-47 (interpreter /nix/store/wb6rhpznjfczwlwx23zmdrrw74bayxw4-glibc-2.42-47/lib/ld-linux-x86-64.so.2)
  • Toolchain: gcc (GCC) 15.2.0, meson 1.9.1
  • Build: asan (xce.build)
  • Code: scheduler-framework @ 19be145d-dirty
  • Deployment: any (found by source reading; confirmed by the RED test of the fix)

Reproduction

  1. cd src/frontend/apiserver && swag init -g cmd/main.go -o /tmp/x: fails as above.
  • Frequency: deterministic (by code reading; confirmed by the RED test of the fix)
  • Evidence: the code sites quoted in Description; no logs kept.

Root cause

TODO: required for fixed/partial

Fix

TODO: required for fixed/partial

Verification

  • Test: TODO: name + file; RED before the fix, GREEN after
  • Suites: TODO: suite results and build profile
  • Live: TODO: soak/deploy run, or n/a and why

References

  • Related: none