Harden check_requests against per-tournament failures #2
Loading…
Reference in a new issue
No description provided.
Delete branch "harden-check-requests"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Wrap each tournament's info/requests processing in try/except so a single API error, timeout, or malformed record no longer aborts the entire notification batch. Also skip a tournament when
_get_requestsreturns None (non-200 response) instead of raising onset(None).🤖 Generated with Claude Code
mentioned in commit
7d0139d8d5