fix(ci): apply lobbying-fetch timeout fix to update-weekly.yml too - #112
Merged
Conversation
#111 fixed the 45-min timeout on the lobbying-fetch step in update-data.yml ("Update Data Only"), but missed that update-weekly.yml ("Weekly Update (Data + Charts)") — the workflow that actually failed 3 weeks running (#108/#109/#110) and runs on the Monday schedule — maintains its own duplicate copy of the same steps. It still had timeout-minutes: 45 and no PYTHONUNBUFFERED. Same fix, same rationale as #111: timeout-minutes 45 -> 90, PYTHONUNBUFFERED=1. Restores parity between the two files' fetch sections. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
nesanders
force-pushed
the
fix/weekly-workflow-timeout-parity
branch
from
August 22, 2026 19:03
97e901e to
926cfc8
Compare
This was referenced Aug 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
#111 fixed the 45-min timeout on the lobbying-fetch step, but only in
update-data.yml("Update Data Only"). It missed thatupdate-weekly.yml("Weekly Update (Data + Charts)") — the workflow that actually failed 3 weeks running (#108, #109, #110) and runs on the Monday schedule — maintains its own duplicate copy of the same fetch steps. That file still hadtimeout-minutes: 45and noPYTHONUNBUFFERED.Running the weekly workflow as-is would just time out again.
Fix
Same change as #111, applied to
update-weekly.yml:timeout-minutes: 45 → 90,PYTHONUNBUFFERED: "1". Restores parity between the two files' fetch sections (confirmed identical via diff).🤖 Generated with Claude Code