chore: classify session-limit sensor outages separately from weekly-limit - #545
Open
essentialbit wants to merge 6 commits into
Open
chore: classify session-limit sensor outages separately from weekly-limit#545essentialbit wants to merge 6 commits into
essentialbit wants to merge 6 commits into
Conversation
…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.
4 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
scripts/check_sensor_health.py's signature classifier only had aweekly_limitpattern; 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 genericother:bucket instead.session_limitsignature 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 OKclassify()against the actual20260801-135013.log/20260801-145043.logoutage logs — now returnssession_limit(previously would have beenother: "You've hit your session limit...")