Skip to content

chore: classify session-limit sensor outages separately from weekly-limit - #545

Open
essentialbit wants to merge 6 commits into
mainfrom
chore/sensor-session-limit-signature-20260801
Open

chore: classify session-limit sensor outages separately from weekly-limit#545
essentialbit wants to merge 6 commits into
mainfrom
chore/sensor-session-limit-signature-20260801

Conversation

@essentialbit

Copy link
Copy Markdown
Owner

Summary

  • scripts/check_sensor_health.py's signature classifier only had a weekly_limit pattern; a distinct "session limit" outage (resets same-day at a fixed hour, not weekly) hit 2026-08-01 13:50-15:51 (3 consecutive rc=1 cycles) and fell into the generic other: bucket instead.
  • Adds a session_limit signature so future diagnosis can tell the two outage classes apart (they imply different expected recovery windows: same-day vs Friday-reset).

Self-directed tooling improvement (no feature_backlog/consensus item was eligible this cycle — backlog empty at the 0.55 threshold).

Test plan

  • venv/bin/python3 -c "from main import *" — import OK
  • Ran classify() against the actual 20260801-135013.log/20260801-145043.log outage logs — now returns session_limit (previously would have been other: "You've hit your session limit...")

Saifodius and others added 5 commits August 1, 2026 18:08
…imit

check_sensor_health.py's signature list only recognized "weekly limit"
outages, so the distinct "session limit" outage observed 2026-08-01
13:50-15:51 (3 consecutive rc=1 cycles, resets same-day at a fixed hour
rather than weekly) fell into the generic "other" bucket instead of being
cleanly classified -- misleading for future diagnosis since the two imply
different expected recovery windows.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant