Repository navigation
fix(tui): let quit abandon the background update check - #162
Merged
Merged
Conversation
Vycari Review (shadow)Shadow round 2 on 838b16f. This comment is non-gating and needs no response: it is collected to measure agreement with the current reviewer. The round's verdict is the Vycari Review (shadow) check run. Open: P0 0 · P1 0 · P2 0 · confirmed fixed 0 · withdrawn 0 Judge's notes No candidate findings were raised. No open findings this round. |
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.
Human overview
Quitting Pepper no longer waits for a slow background release lookup to finish. Closing the TUI stops further fallback lookups and discards any late result. Fixes #160.
AI reviewer
tui/app.py: run the optional update check on a named daemon thread, following the existing streamed-turn pattern. Asyncio no longer joins this lookup during shutdown. Keep using_postand_on_update_availableto drop results once closing begins._version.py: add an optionalshould_stopcallback. Check it before starting each request and before caching or returning a network result. The active request can finish on its daemon thread; it is not forcibly interrupted.simplifyandcode-reviewskills are unavailable in this session. A manual simplification and correctness review found no additional changes needed.Verification on main at
0f11c70, using the locked dev environment:uv run --no-sync ruff format --check: 122 files already formatted.uv run --no-sync ruff checkanduv run --no-sync ty check src/pepper_cli/: passed.uv run --no-sync pytest -q --cov --cov-report=json:coverage-summary.json: 2,531 passed, 2 skipped; 94.98 percent line coverage, passing the unchanged 88 percent floor.NO_COLORwas unset for color-rendering tests and local test-server socket access was enabled. The suite reported the same nine existingpepper-person-streamteardown warnings seen before this fix; no update-check warnings.git diff --check: passed.Checklist (repo-specific)
uv run ruff format --checkanduv run ruff checkclean (no new lint ignores)uv run ty check src/pepper_cli/cleanuv run pytestpasses; coverage floor in.claude/maintainerd.jsonnot loweredSKILL.mdunaffected because agent commands and output are unchanged

Confidence Score: 5/5
The PR appears safe to merge, with the previous test-coverage gap addressed.Summary
Quitting the TUI no longer waits for the background release check.
Diagram
%%{init: {'theme': 'neutral'}}%% flowchart TD A[TUI starts] --> B[Daemon thread checks for updates] B --> C{App closing?} C -->|No| D[Continue lookup and show result] C -->|Yes| E[Skip fallback requests and discard result] Q[User quits] --> F[TUI exits without joining check thread] Q --> CReviews (2) · Last reviewed commit: "test(updates): cover successful response..." · Reviewed by Greptile