lsmith/nextcloud-classification
1
1
Fork
You've already forked nextcloud-classification
0

Fix dashboard: durable recent-filed source, time-windowed errors, real auto/manual split #1

Merged
lsmith merged 1 commit from fix/dashboard-durable-filed-and-error-window into main 2026年06月24日 21:54:30 +02:00

The weekly-review dashboard showed two misleading things even while the
classification pipeline was healthy:

  • "Recently Filed" read the notification queue, which the digest truncates of
    filed rows after every send — so once a digest had run the table showed
    nothing. It now reads the durable pending_meta/ sidecars (the system of
    record) unioned with the not-yet-truncated queue, deduped, is_filed-filtered,
    within a days window. Human-filed docs surface via the reviewed=True flag.

  • "Recent Errors" had no time filter, so a weeks-old error read as current.
    read_errors()/api/errors now take a days window and the dashboard passes its
    period selector.

  • The metric cards/pie read .analytics.json, which only ever recorded manual
    saves (so auto-classified was hardcoded ~0%). The counts are now derived from
    the sidecars: filed = is_filed; manual = reviewed=True; auto = the rest. A
    short TTL cache fronts the per-load sidecar scan, shared by both endpoints.

The weekly-review dashboard showed two misleading things even while the classification pipeline was healthy: - "Recently Filed" read the notification queue, which the digest truncates of filed rows after every send — so once a digest had run the table showed nothing. It now reads the durable pending_meta/ sidecars (the system of record) unioned with the not-yet-truncated queue, deduped, is_filed-filtered, within a days window. Human-filed docs surface via the reviewed=True flag. - "Recent Errors" had no time filter, so a weeks-old error read as current. read_errors()/api/errors now take a days window and the dashboard passes its period selector. - The metric cards/pie read .analytics.json, which only ever recorded manual saves (so auto-classified was hardcoded ~0%). The counts are now derived from the sidecars: filed = is_filed; manual = reviewed=True; auto = the rest. A short TTL cache fronts the per-load sidecar scan, shared by both endpoints.
The weekly-review dashboard showed two misleading things even while the
classification pipeline was healthy:
- "Recently Filed" read the notification queue, which the digest truncates of
 filed rows after every send — so once a digest had run the table showed
 nothing. It now reads the durable pending_meta/ sidecars (the system of
 record) unioned with the not-yet-truncated queue, deduped, is_filed-filtered,
 within a days window. Human-filed docs surface via the reviewed=True flag.
- "Recent Errors" had no time filter, so a weeks-old error read as current.
 read_errors()/api/errors now take a days window and the dashboard passes its
 period selector.
- The metric cards/pie read .analytics.json, which only ever recorded manual
 saves (so auto-classified was hardcoded ~0%). The counts are now derived from
 the sidecars: filed = is_filed; manual = reviewed=True; auto = the rest. A
 short TTL cache fronts the per-load sidecar scan, shared by both endpoints.
Sign in to join this conversation.
No reviewers
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lsmith/nextcloud-classification!1
Reference in a new issue
lsmith/nextcloud-classification
No description provided.
Delete branch "fix/dashboard-durable-filed-and-error-window"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?