Update Reviews asked appreviews about one game at a time, two seconds a game. At 9,847 games it ran into GitHub's six-hour limit on 2026-10-23 and was stopped with nothing saved; five of its ten runs before that were cancelled while waiting. - SteamClient.fetch_items(): GetItems for a whole catalogue, a failed batch costing only its own ids (the anti-cheat sweep now uses it). - update_reviews.py reads review_summary() for every game, ~2 minutes, daily. Steam floors its percentage; reviews_from_summary() floors appreviews in integers too, so an ingest and the refresh agree. A count of 0 is never written on GetItems' word (it said 0 for a game with thousands): a stored percentage or "N/A" is asked on appreviews, at most 300 a run. last_updated moves on a change, and on a 14-20 day heartbeat that keeps the site's 30-day "stale" badge quiet without rewriting every record every run. - core/budget.py: JOB_BUDGET_MINUTES. Past it process_batch() starts no further game, so a job saves what it did instead of being killed; a ::warning:: when a loop used three quarters of its budget. - rotation.cycle_for() / daily_order(): cycles that grow with the catalogue as multiples of their base, and an order that changes daily. - The player-count loops skip the batch pauses meant for store pages (Top Online ~27 min instead of 48) and take a deadline, like update_all_full(). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
41 lines
1.3 KiB
YAML
41 lines
1.3 KiB
YAML
name : Update Reviews
|
|
|
|
# Every game's review summary from IStoreBrowseService/GetItems, fifty games a
|
|
# request: about two minutes for the whole catalogue (scripts/update_reviews.py
|
|
# has the rules). It used to ask appreviews about one game at a time and, at
|
|
# 9,800 games, ran into GitHub's six-hour limit with nothing saved.
|
|
|
|
on :
|
|
schedule : [ { cron : '0 6 * * *' } ]
|
|
workflow_dispatch :
|
|
inputs :
|
|
dry_run :
|
|
description : 'Dry run: read Steam, write nothing'
|
|
type : boolean
|
|
default : false
|
|
permissions : { contents : write }
|
|
# queue: max - a run that finds another data job running waits its turn
|
|
# (first in, first out) instead of evicting the run already waiting.
|
|
concurrency :
|
|
group : data-write
|
|
cancel-in-progress : false
|
|
queue : max
|
|
jobs :
|
|
reviews :
|
|
runs-on : ubuntu-latest
|
|
timeout-minutes : 60
|
|
steps :
|
|
-
|
|
uses : actions/checkout@v6
|
|
# main as it is when the job STARTS: a run that waited its turn must
|
|
# work on what the job before it committed.
|
|
with : { ref : main }
|
|
-
|
|
uses : actions/setup-python@v6
|
|
with : { python-version : '3.15' }
|
|
-
|
|
run : chmod +x ./bash/reviews.sh && ./bash/reviews.sh
|
|
env :
|
|
JOB_BUDGET_MINUTES : '40'
|
|
REVIEWS_DRY_RUN : ${{ inputs.dry_run }}
|