31 releases 31 tags

RSS feed

• v1.12.1 54fe96f81f

  Compare

  v1.12.1 — count the summoners a poll cycle skipped Stable

  joeyr released this 2026-08-03 13:30:20 -05:00 | 0 commits to main since this release

  A correction to the LoL polling cycle's own health line, which could report a
  cycle as clean while a watched summoner had silently dropped out of it.

  Fixed

  • Polling cycle complete now reports skipped. A spectator-v5 call that
    fails is caught inside pollSummoner, which returned no_change — the same
    value as a successful poll that found nothing new. The cycle's errors
    counter only counts polls that throw, so a summoner lost to a timeout was
    reported inside errors=0 with summonersPolled still claiming full
    coverage. Live logs showed exactly that: a 10s spectator timeout at 11:27:57
    followed by Polling cycle complete | errors=0 at 11:30:04.
  • pollSummoner returns a new 'skipped' outcome (see the PollOutcome type)
    for both failure branches — the transient network error and the
    response-mapping TypeError — since neither actually checked the summoner.
    'no_change' now means only what it says: we looked, and nothing had changed.

  Notes on the design

  • The counters are deliberately separate. errors stays "the poll threw out
    of pollSummoner"; skipped is "pollSummoner handled it and gave up on
    this summoner for this cycle". Both mean not polled, and neither is a fault
    worth waking up for on its own — spectator-v5 timeouts run at a low
    single-digit percent and the next cycle picks the summoner back up.
  • No retry was added. A skipped summoner costs one 5-minute cycle: a game
    start is announced late, and a game end is caught next cycle or by the hourly
    stale sweep. The reason to count the skips is that this is the number that
    would have to climb before any of that stopped being true, and until now it
    was not visible anywhere.

  Downloads

  • Source code (ZIP)
    0 downloads
  • Source code (TAR.GZ)
    0 downloads