fix: only advance update/lastCheck after a completed check (#37) #44

Merged
the_og merged 1 commits from fix/37-update-lastcheck into main 2026-07-12 13:00:37 -04:00
Owner

Closes #37.

update/lastCheck was stamped before the worker started, so an offline launch burned the once-per-day check and suppressed retries for 24 h. The timestamp now advances only in the completion handler when the request actually returned data; a failed/offline check leaves it untouched so the next launch retries.

Tests + ruff clean. (Implemented by a delegated agent; reviewed.)

🤖 Generated with Claude Code

Closes #37. `update/lastCheck` was stamped before the worker started, so an offline launch burned the once-per-day check and suppressed retries for 24 h. The timestamp now advances only in the completion handler when the request actually returned data; a failed/offline check leaves it untouched so the next launch retries. Tests + ruff clean. (Implemented by a delegated agent; reviewed.) 🤖 Generated with [Claude Code](https://claude.com/claude-code)
the_og added 1 commit 2026-07-12 12:59:43 -04:00
fix: only advance update/lastCheck after a completed check (#37)
CI / Lint (ruff) (pull_request) Successful in 7s
CI / Tests (py3.10) (pull_request) Successful in 9s
CI / Tests (py3.12) (pull_request) Successful in 8s
f5c9780948
Closes #37

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
the_og merged commit 6a91f830dc into main 2026-07-12 13:00:37 -04:00
the_og deleted branch fix/37-update-lastcheck 2026-07-12 13:00:37 -04:00
Sign in to join this conversation.