Repository navigation
perf(home): coalesce overlapping session refresh scans - #156
Merged
Merged
Conversation
Owner
Author
|
Reviewed the session-refresh coalescing and added a regression for a new chat appearing after a shared full scan started. The newer first page now survives that older scan's completion on both Home and Chats. PR CI passed; locally, full analysis and 1,338 tests passed. The combined tree with PR #152 passed analysis and 1,364 tests. This only partially addresses #149; that issue stays open pending transfer measurement and the separate transport work. |
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
Partially addresses #149 (app-side overlapping session refreshes). This does not implement a server cursor, transcript-tail delta, durable
/v1/runstransport, WebSocket capability contract, or server compression. Those require separate contracts or tests; the issue should remain open.Verification
flutter test --no-pub: 1,338 tests passedflutter analyze --no-pub lib/core/screens/workspace_screen.dart test/workspace_home_progressive_test.dart: no issuesgit diff --check: cleanPlease test the request counts on a real v2.1.23+ gateway before claiming a transfer-volume reduction.