Repository navigation
Conversation
…surement land The test read the row window once after a fixed two-frame settle. In CI it once read the first window (row 3 where row 48 was due), with the focused row still mounted, so the failure was the read, not the island. The scroll owner drops a scroll event while a measurement frame is pending, and the window then follows that frame. A second scroll report and two more frames now let every scheduled measurement land before the rows are read.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR Analysis Report
Generated by PR Enrichment workflow | View current CI run |
|
AI review status for this pull request.
|
There was a problem hiding this comment.
Changes requested: the test change is small and the case passes, but its comment and the description explain it with a cause the code does not support.
- The new comment at
useTableColumnsVirtualization.test.tsx:1021-1024, the title and the description say focusing the cell schedules a measurement frame that lands after the two-frame settle, but focusing schedules no frame and a frame pending when the scroll lands already runs in the first settle frame (the existing late-frame case asserts this), so what the change adds is a second scroll report; please reword them to what is established: the failure did not reproduce, and the second scroll report publishes the scroll position again.
Keeping the second scroll is fine once the comment says so; the late-frame case still covers a scroll that lands while a measurement is pending.
Claims and files checked
Review mode: full; reason: no-earlier-review
- Only contributors running the Table suite are affected and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due: not verifiable (no run is linked, and it did not reproduce).
- The failure was the single read, not a lost focus island: consistent with the reported failure, where the window never moved.
- After each scroll the test reports one more scroll and waits two more frames: verified (the existing helper, called at lines 1025 and 1035).
- The scroll owner skips a scroll event while a measurement frame is pending: verified (
useScrollableArea.ts:450-453). - Focusing the cell can schedule such a frame: false (focus requested no frame and made no DOM change the scroll owner observes).
- That frame's measurement can land after the two-frame settle: false (it runs in the first settle frame and publishes the scroll position; the late-frame case at line 991 asserts the window follows).
- No retry and no timeout change: verified (no retry option or timeout edit).
- No changeset because the change is test-only: verified.
- Delayed frames never reproduced the stale window locally: consistent (the case without the new wait passes with frames 80 ms late).
- The Table suites pass, 908 of 908: the suites pass (906 of 906 in the Table folder, two runs); the exact count was not reproduced.
- Open pull requests #11844, #11826 and #11197 also edit this file: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: finding (the comment at lines 1021-1024).
There was a problem hiding this comment.
Changes requested: the new comment and the title now say what the change does, but one line of the description still gives the earlier explanation.
- The description's After line says the test "lets every scheduled measurement land before it reads the rows", but the base already did that (no measurement frame is pending when it reads the rows, and focusing the cell schedules none), so please reword it to what the change adds, for example "the test reports the scroll a second time and waits two more frames before it reads the rows".
The case passes on this head, and the earlier note on the test comment is resolved.
Claims and files checked
Review mode: incremental; reason: none
- Only contributors running the Table suite are affected and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due with the focused row still mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure was the single read, not a missing focus island: consistent with the reported failure, where the window never moved.
- After the change, the test lets every scheduled measurement land before it reads the rows: false as a change (no measurement frame is pending at the base's read point).
- After each scroll the test reports one more scroll and waits two more frames: verified (the existing helper, called at lines 1025 and 1035).
- The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll when no measurement is pending).
- The failure did not reproduce, so no cause is claimed: matches the new comment and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 991).
- No retry and no timeout change: verified.
- No changeset because the change is test-only: verified.
- Frames delayed by 0, 80 or 200 ms never reproduced the stale window: consistent (the case without the new wait passes at each delay).
- The Table suites pass, 908 of 908: the suites pass (906 of 906 in the Table folder, two runs); the exact count was not reproduced.
- Open pull requests #11844, #11826 and #11197 also edit this file: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear (the comment at lines 1021-1024 now says what the code does).
There was a problem hiding this comment.
Approved: CI passed on this head, and nothing is left for the author.
The focus case re-sends the scroll and waits two more frames before it reads the rows, its assertions are unchanged, and every description claim matches the code.
Claims and files checked
Review mode: same-head; reason: none
- Only contributors running the Table suite are affected, and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due with the focused row still mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure was the test's single read, not a missing focus island: consistent with the reported failure, where the window never moved.
- After each scroll, the test reports the scroll a second time and waits two more frames before it reads the rows: verified (the existing helper, called at lines 1025 and 1035).
- The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll when no measurement is pending).
- The failure did not reproduce, so no cause is claimed: matches the comment at lines 1021-1024 and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 991).
- No retry and no timeout change: verified.
- No changeset, because the change is test-only: verified.
- Delaying frames by 0, 80 or 200 ms never reproduced the stale window, and focus stayed on the cell: consistent (the case without the new wait passes at each delay).
- The Table suites pass, 908 of 908, three runs in a row: the suites pass (906 of 906 in the Table folder, and this file 40 of 40 in CI on this head); the exact count was not reproduced.
- Open pull requests #11844, #11826 and #11197 also edit this file: verified.
- The pull request lands after an approval of this exact head, CI, then the merge queue: consistent (CI passed on this head).
- The title, that the test reports the scroll again before reading rows: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear.
|
/approve-spec e0536f1 |
|
/approve-spec 859463e |
There was a problem hiding this comment.
Approved pending CI: CI has not run on this head yet, because a draft runs no CI. Mark the pull request ready for review so CI runs; nothing else is left for the author.
The merge of main leaves the patch unchanged: the focus case still re-sends the scroll and waits two more frames before it reads the rows, its assertions are unchanged, and every description claim matches the code.
Claims and files checked
Review mode: carry-forward; reason: none
- Only contributors running the Table suite are affected, and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due with the focused row still mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure was the test's single read, not a missing focus island: consistent with the reported failure, where the window never moved.
- After each scroll, the test reports the scroll a second time and waits two more frames before it reads the rows: verified (the existing helper, called at lines 1025 and 1035).
- The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll when no measurement is pending).
- The failure did not reproduce, so no cause is claimed: matches the comment at lines 1021-1024 and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 991).
- No retry and no timeout change: verified.
- No changeset, because the change is test-only: verified.
- Delaying frames by 0, 80 or 200 ms never reproduced the stale window, and focus stayed on the cell: consistent (the case without the new wait passes at each delay).
- The Table suites pass, 908 of 908, three runs in a row: they passed with this same patch before the merge of
main(906 of 906 in the Table folder, and this file 40 of 40 in CI); not yet run on this head. - Open pull requests #11844, #11826 and #11197 also edit this file: verified (all three are open).
- The pull request lands after an approval of this exact head, CI, then the merge queue: consistent (CI has not run on this head yet).
- The title, that the test reports the scroll again before reading rows: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear.
|
/approve-spec 874d588 |
There was a problem hiding this comment.
Approved pending CI: CI has not run on this head yet, because the run that started when the pull request was marked ready found no room under the CI ceiling and was cancelled. Re-run all jobs of that CI run (or push later) so CI runs; nothing else is left for the author, and the patch is unchanged since the last review.
#11844 has since landed on main and edits this file; this head merges cleanly with it, and the focus case passes on the merged code.
Claims and files checked
Review mode: same-head; reason: none
- Changed rules since the last review (0): none.
- Only contributors running the Table suite are affected, and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due with the focused row still mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure was the test's single read, not a missing focus island: consistent with the reported failure, where the window never moved.
- After each scroll, the test reports the scroll a second time and waits two more frames before it reads the rows: verified (the existing helper, called at lines 1059 and 1069).
- The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll when no measurement is pending).
- The failure did not reproduce, so no cause is claimed: matches the comment at lines 1055-1058 and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 1025).
- No retry and no timeout change: verified.
- No changeset, because the change is test-only: verified.
- Delaying frames by 0, 80 or 200 ms never reproduced the stale window, and focus stayed on the cell: consistent with an earlier probe of the same case.
- The Table suites pass, 908 of 908, three runs in a row: they pass on this head and on this head merged with the current
main(937 of 937 in the Table folder there, after newer cases landed; this file 43 of 43, three runs). - #11844, #11826 and #11197 also edit this file, and this one merges
mainafter them: #11826 and #11844 have landed, and this head merges cleanly with the currentmainand passes there; #11197 is still an open draft. - The pull request lands after an approval of this exact head, CI, then the merge queue: consistent (CI has not run on this head yet: its run found no room and was cancelled).
- The title, that the test reports the scroll again before reading rows: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear.
|
/approve-spec fabb470 |
There was a problem hiding this comment.
Approved pending CI: CI started on this head when the pull request was marked ready for review, and the UI test jobs that run this file have passed, but the other required jobs are still running. Nothing is left for the author.
The focus case now re-sends the scroll and waits two more frames before it reads the rows; its assertions are unchanged, and every checkable claim in the description matches the code.
Claims and files checked
Review mode: same-head; reason: none
- Only contributors running the Table suite are affected, and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due while the focused row stayed mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure came from the test's single read, not a missing focus island: consistent with the reported failure, where the row window never moved.
- After each scroll, the test reports the scroll again and waits two more frames before it reads the rows: verified (the existing
landWriteshelper, called at lines 1081 and 1091). - The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll event when no measurement is pending,
useScrollableArea.ts:450-496). - No cause is claimed for the failure: matches the comment at lines 1077-1080 and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 1047).
- No retry and no timeout change: verified.
- No changeset, because the change is test-only: verified.
- Delaying frames by 0, 80 or 200 ms never reproduced the stale window: not rerun on this head; an earlier probe of the same case agrees.
- The Table suites pass, 908 of 908, three runs in a row: they pass on this head (CI's UI test jobs, this file 43 of 43), with newer cases landed since.
- #11844, #11826 and #11197 also edit this file, and this one merges
mainafter them: #11826 and #11844 have landed and this head includes both; #11197 is still an open draft. - The pull request lands after an approval of this exact head, CI, then the merge queue: consistent (CI is running on this head).
- The title, that the test reports the scroll again before reading rows: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear.
|
/approve-spec 3318894 |
There was a problem hiding this comment.
Approved pending CI: this head only merges main, so the change is identical to the one approved before, but CI has not run on it because the pull request is a draft. CI runs once the pull request is marked ready for review.
The focus case re-sends the scroll and waits two more frames before it reads the rows; its assertions are unchanged, and every checkable claim in the description matches the code.
Claims and files checked
Review mode: carry-forward; reason: none
- Only contributors running the Table suite are affected, and no component code changes: verified (one test file, 6 added lines).
- The case failed once in CI, reading row 3 where row 48 was due while the focused row stayed mounted: not verifiable (no run is linked, and it did not reproduce).
- The failure came from the test's single read, not a missing focus island: consistent with the reported failure, where the row window never moved.
- After each scroll, the test reports the scroll again and waits two more frames before it reads the rows: verified (the existing
landWriteshelper, called at lines 1081 and 1091). - The second scroll report publishes the scroll position again: verified (the scroll owner publishes on a scroll event when no measurement is pending,
useScrollableArea.ts:450-496). - No cause is claimed for the failure: matches the comment at lines 1077-1080 and the title.
- The late-frame case still covers a scroll that lands while a measurement is pending: verified (the case at line 1047).
- No retry and no timeout change: verified.
- No changeset, because the change is test-only: verified.
- Delaying frames by 0, 80 or 200 ms never reproduced the stale window: not rerun; an earlier probe of the same case agrees.
- The Table suites pass, 908 of 908, three runs in a row: not rerun on this head; CI passed this file 43 of 43 and every test shard on the previous head, whose patch is identical.
- #11844, #11826 and #11197 also edit this file, and this one merges
mainafter them: #11826 and #11844 have landed and this head includes both; #11197 is still an open draft. - The pull request lands after an approval of this exact head, CI, then the merge queue: consistent; CI waits for the draft to be marked ready.
- The title, that the test reports the scroll again before reading rows: verified.
packages/core/src/Table/plugins/virtualization/useTableColumnsVirtualization.test.tsx: clear.
User impact
useTableColumnsVirtualization.test.tsxfailed once in CI. It read the first row window (row 3 where row 48 was due) while the focused row was still mounted. So the failure was the test's single read, not a missing focus island.What changed
scrollBoth, the test reports one more scroll and waits two more frames (landWrites) before reading the rows. The second scroll report publishes the scroll position again. The CI failure didn't reproduce locally, so this doesn't claim a cause. The existing late-frame case still covers a scroll that lands while a measurement is pending.Evidence
Scope
Test-only (Table virtualization).
Owner: Astryx fix-loop lane 0. Land path: CodeBunny approval of the exact head, CI, then the merge queue.
Overlap checked: #11844, #11826, #11197 (they change column-window scroll behaviour and add their own cases in this file; this changes only the one rows-and-columns focus case read, so it stays separate and merges main after them)