-
Notifications
You must be signed in to change notification settings - Fork 94
fix(chat): kick load-older from items effect when viewport cannot scroll #31826
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dvargasfuertes
merged 4 commits into
main
from
apollo/fix-underfilled-viewport-load-older
May 23, 2026
+156
−11
Merged
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
ef9e2fa
fix(chat): kick load-older from items effect when viewport can't scroll
9ab8e1f
test(chat): regression for items-effect underfilled-viewport kick
39e1a81
chore(chat): trim verbose comment on underfilled-viewport kick
vellum-apollo-bot[bot] e021b2c
fix(chat): read loading flags from closure to address Codex P1
vellum-apollo-bot[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This new items-effect load kick can stall after the first page because it relies on
classificationcomputed fromlatestRef.current(which is only refreshed in a lateruseEffect). In the common sequenceisLoadingOlder: false -> true -> falsewhile prepended items arrive, the layout effect on the prepend render still sees the previousisLoadingOlder=truesnapshot, soshouldLoadOlderis false and no second kick fires even if the viewport is still unscrollable andhasMoreremains true. That leaves the transcript stuck again for conversations that need multiple older pages to overflow.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch — addressed in e021b2c.
The items effect now reads
hasMore,isLoadingOlder,conversationKey,items, andonLoadOlderfrom the closure instead oflatestRef.current, and those flags are in the dep array. The stale-snapshot window you described (the prepend render runs the layout effect before the latestRef-refreshing useEffect fires) was a real bug — confirmed by tracing thefalse → true → falsesequence.Added a regression test (
chain-load: false→true→false sequence kicks again when still underfilled) that walks the three-step sequence and asserts a second kick fires on step 3 when the viewport is still underfilled. Would have caught this exact issue if the dispatch read from a stale ref.