2 Known Issues And Diagnostics
Forgejo Actions edited this page 2026-10-24 19:43:45 +00:00

Known Issues and Operator Diagnostics

This page summarizes the open issues that matter most to operators. The live, authoritative list is KNOWN_ISSUES.md; use it for exact issue states and fixes.

  • Security audit findings: high-severity IDORs around contributions and candidate accept/reject (ISSUE-010, ISSUE-011, ISSUE-012), export role checks (ISSUE-014, ISSUE-016), and sessions trusted for up to 30 days without database revalidation (ISSUE-015) remain open — accepted risk under the single-operator/family deployment model (audit 2026-10-24).
  • Rotated-image boxes: the plants worker still misses exif_transpose, so plant boxes can be wrong on rotated photos (ISSUE-023); face and thing/semantic lanes are fixed.
  • CI: scoped PR test jobs can skip the JVM suites on the fallback-smoke path (ISSUE-091, ISSUE-099), so a green scoped run is not proof that :apps:api:test ran.

One dedicated diagnostic helps during the supervised people migration: GET /api/admin/operator-status exposes a peopleGenericConsistency block. It compares legacy person_records and assignments with the generic class-instance state and reports either consistent or drift_detected. Drift means generic People state should not yet be treated as the sole authority. See People Generic Consistency for details.

Details