ChessCalcNextTour/bots
vrubel 77c8a87e16
All checks were successful
CI/CD Pipeline / build-and-deploy (push) Successful in 4s
fix: stop burning request limit on finished tournaments + reset stale result counts
check_all_subscriptions: always call update_round even for the final round.
Previously, last_round_done was never updated past the second-to-last round
(because pairings aren't calculated for the last round). This kept
quick_rd > last_round_done forever on finished tournaments, triggering a full
fetch (~22 HTTP requests) every 5 minutes — causing 26k+ daily requests to
chess-results.com against a 2000-request daily limit.

rescan_existing_tournaments: when correcting player_sno, also reset
last_results_count to 0. Stale counts from a wrong player (from the FIDE ID
parsing bug) could be higher than the real player's count, permanently
suppressing result notifications for the correct player.

DB patched directly: last_results_count reset to 0 for subs 40 (Vrubel)
and 47 (Aslanbekov) so they re-learn correct scores on next fetch.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2026-06-22 15:19:39 +00:00
..
__init__.py Добавлены Telegram-боты (клиентский + админский) 2026-06-14 20:39:19 +00:00
admin_bot.py Добавлен счётчик уникальных пользователей за сегодня в /stat 2026-06-15 18:12:42 +00:00
client_bot.py fix: reduce chess-results.com request volume by ~20-50x 2026-06-21 07:47:38 +00:00
stats.py Добавлен счётчик уникальных пользователей за сегодня в /stat 2026-06-15 18:12:42 +00:00
tracker.py fix: stop burning request limit on finished tournaments + reset stale result counts 2026-06-22 15:19:39 +00:00