fix(nudge): throttle idle goal notification scans - #887
Merged
huangzesen merged 1 commit intoJul 24, 2026
Merged
Conversation
huangzesen
force-pushed
the
fix/issue-751-goal-nudge-throttle-telegrambot
branch
from
July 22, 2026 06:49
813b893 to
561221b
Compare
huangzesen
force-pushed
the
fix/issue-751-goal-nudge-throttle-telegrambot
branch
from
July 23, 2026 08:30
561221b to
5984ed8
Compare
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
NotificationStore.snapshot(allow)boundary; no direct filesystem reads or persistent throttle stateTests
tests/test_goal_notification.py— 8 passedgit diff --check— passedGoal-state changes can be observed up to 10 seconds later, by design.
Fixes #751