Repository navigation
fix(release): stop CI progress spam from spinner ticks - #181
Merged
Merged
Conversation
Rich's Progress bar auto-refreshes ~10x/sec by default. On a real terminal that just redraws the same line in place, but GitHub Actions' live log tail can't overwrite a line, so every refresh became its own permanent log line -- several near-duplicate lines per file while ffmpeg/ffmpeg-normalize processed it, not one per file. Disable auto_refresh on CI and refresh manually only when progress.advance() actually happens, so CI logs get one line per item of real progress instead of one per spinner tick. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
pfeerick
force-pushed
the
fix/release-ci-progress-spam
branch
from
August 30, 2026 03:41
e5dda7b to
9ad1d71
Compare
5 tasks done
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
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.
Summary
Progressbar auto-refreshes ~10x/sec by default. On a real terminal that just redraws the same line in place, but GitHub Actions' live log tail can't overwrite a line — so every refresh became its own permanent log line, producing several near-duplicate lines per file while ffmpeg/ffmpeg-normalize processed it (e.g. 4 lines for the same file, differing only by spinner glyph), instead of one line per file actually finished.auto_refreshwhenCIis set, and callprogress.refresh()manually only right afterprogress.advance(), so CI logs get one line per unit of real progress instead of one per spinner tick. Local/interactive runs are unaffected (still auto-refresh live as before).Test plan
CI=trueagainst an isolated fixture and confirmed the archive-creation step now emits one progress frame per zip created instead of a stream of spinner-tick duplicates.release.pyshows one log line per file/archive processed rather than several per item.