Skip to content

Fix: cap the widget failure log per widget - #517

Merged
SandObserver merged 1 commit into
mainfrom
fix/failure-log-cap
Oct 19, 2026
Merged

SandObserver merged 1 commit into
mainfrom
fix/failure-log-cap

Conversation

@SandObserver

Copy link
Copy Markdown
Owner

Summary

  • Keep at most 16 failing keys per widget in the failure log. A new key past the cap is neither stored nor logged.
  • Pass the widget id and the existing per-widget cap from GET /api/widget-data/:id, whose key includes the request's endpoint value.
  • Change failed() to take { now, group, maxPerGroup } as its last argument.

Testing
All green. Added tests for the per-widget cap and for 40 distinct endpoint values producing 16 lines.

Changelog

Checklist

  • Stays within the project constraints: one container, no runtime dependencies, no build step (see CONTRIBUTING.md).
  • Tests added or updated for new logic, and the full suite, lint, and typechecks pass.
  • Docs updated if behavior or configuration changed.

@SandObserver SandObserver added the bug Something isn't working label Oct 19, 2026
@SandObserver
SandObserver merged commit c04b554 into main Oct 19, 2026
6 checks passed
@SandObserver
SandObserver deleted the fix/failure-log-cap branch October 19, 2026 21:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant