test(desktop): stop four E2E specs racing scroll settles and focus by matt2e · Pull Request #8743 · block/buzz

matt2e · 2026-10-30T11:58:22Z

Summary

Units 2–5 of the 23–30 Oct desktop Playwright flake audit: four E2E specs that raced scroll settles and focus. All four fixes are test-only. This is one of six PRs split from the reviewed flakey-tests branch (siblings below).

`navigation.spec.ts:472` "composer Buzz chip labels wrap without orphaning their icons"

11 jobs failed in the window, 6 of them after the earlier fixes, including 4 of the 7 main runs that carry every fix. Run 40970053997 (Smoke shard 7) failed all three attempts.

Mode A (jobs 122971493553, 123066839967, 123572467962, 123819180597 and retry 2 of 123784825042): fragmentStep is null at :634. Rows key on renderKey = localKey ?? id, and a head refetch or live echo after the ack drops the localKey. The row remounts and loses the 220 px width the test set earlier. Change: re-land the test half of closed fix(desktop): show channel members before joining #6852. Set the width and measure in one expect.poll, and set the width again before each fragment measurement.
Mode B (jobs 123573056202, 123784199542, 123784825042 twice, 123804428893, 123818728963, 123819543461, and 122924164125): the tooltip-centre poll at :667 receives 81.35 or Infinity. Radix Tooltip closes when an ancestor of its trigger scrolls. In the failing attempt, the post-send settle took its last step 21 ms or less before focus. Change: wait for the sent row's message-send-status to clear. Then poll until the timeline sits at its floor and holds there for two animation frames, and only then focus the chip. positionOverFragment asserts data-state is open. There is no retry loop around the race.

`huddle-transcription.spec.ts:637` "animates the responding agent with the shared speaker ring"

Runs: 9 jobs, always Smoke shard 4, attempt 1. On main: 39896948198, 40718743531, 40732061485, 40840949170, 40906253761, 40969965981 and 40983029157. On PRs: Fix duplicate timeline rows while reading history #8715 and perf(relay): route author- and #p-scoped global subscriptions by selector #8666. toBeFocused() at :697 reads inactive.
Cause: useComposerAutofocus runs again once the editor mounts and takes focus from the focused trigger.
Change: wait for message-input to be focused before focusing the trigger, as the same spec already does at :855.

`scroll-history.spec.ts:1289` "fast middle-page scroll settles with continuous mounted coverage"

Runs: 9 jobs. After the fixes: main 40980404335 (job 123819180518) and two attempts on Wait for agent inventory updates in the desktop test #8720. The viewportCoverage poll expects < 100 and receives 200, the bottom spacer.
Cause: the bottom-settle intent armed when the channel first positions survives the prepend and the spec's scrollTop writes. Virtua's re-measure then pulls the list back to the floor.
Change: hover the timeline and wheel up 120 px first, since reader input cancels the intent. Then poll until the timeline is more than 32 px from the floor and steady for two frames.
The commit message calls the cancelling listener listenForReaderScroll, a name introduced by sibling fix(desktop): hold a deep-linked message against bottom settles #8742. On main, the same wheel listener is inline in useVirtualizedBottomSettle, so this fix doesn't depend on that PR.

`custom-emoji.spec.ts:370` "reacting with a custom emoji renders via the loopback media proxy"

Runs: main 40787609859 and 40983029157 (Smoke shard 3), and BUZZ-271: Bound live-session revalidation #8241. The inline "Add reaction" opacity reads "1", not "0".
Cause: the non-modal Radix Popover returns focus to its trigger in a setTimeout(0) after its 100 ms exit animation. That can land after the spec's blur.
Change: wait for the "Open reactions" trigger to be focused, then blur.

Related issue

None found. Sibling #8744 also edits navigation.spec.ts, in a separate hunk. The two merge cleanly in either order. #8622 adds an unrelated test at the end of navigation.spec.ts, and #7812 (stale since 10-06) adds tests elsewhere in three of these files.

Testing

Not run locally, because Playwright bogs this machine down. Flake Check will repeat the touched specs. pnpm typecheck and pnpm check pass. An ad hoc tsc run over the four specs found the same pre-existing errors as on their main copies (navigation 7, huddle 17, scroll-history 0, custom-emoji 2).

Pushed with git push --no-verify, because the pre-push suites fail when the laptop is under load.

Readiness

An agent review of the combined flakey-tests branch (b432453af) found no blockers. buzz-review-completed is not added, because the human test step (AGENTS.md "Before opening a PR", step 3) hasn't happened yet.

Siblings

ci: bound Hermit fetches and let relay builds run without sccache #8739 ci: Hermit fetch deadline and sccache fallback
test(relay): hold the replica's second aux page and move media's DB tests #8740 test(relay): thread_window aux-page hold and api::media Postgres tests
test(mobile): check the title fade's animation, wait 10 s for the alert #8741 test(mobile): RunnerTests title fade and alert wait
fix(desktop): hold a deep-linked message against bottom settles #8742 fix(desktop): deep-linked message hold (product change)
test(desktop): settle five E2E flake classes and clear a draft by Backspace #8744 test(desktop): five settle classes and remote-owned-mentions

🤖 Generated with Claude Code

github-actions · 2026-10-30T12:00:23Z

🔐 Codex Security Review

Note: This is an automated, security-focused review generated by Codex.
Use it as a supplement to human review; false positives are possible.

Scope

Exact PR diff: d342cf141cb3211c8e5a6c74f881cf1d39ad3b12...3b102926b40eccfa555ec0a397e9792ed461aa08

Model: gpt-6.1-sol

💡 Click "edited" above to see earlier reviews for this PR.

Review Summary

Overall Risk: NONE

The authorized range changes synchronization in four desktop end-to-end tests. No concrete security, correctness, or reliability regressions were identified.

Findings

No concrete security, correctness, or reliability findings were identified.

Notes

Review used read-only inspection. Builds and tests were not executed, as instructed.

_{Generated by Codex Security Review |

Requested by: @matt2e |

Workflow run}

jedwards27

🤖 :bot: Jude’s code review agent — REQUEST CHANGES

Reviewed: 1eb67bb525d66448b56d79f98c4ba0e2188b44c5..13171fdd5c763b3538b0c303c48461fa4c1ccd9d (exact head 13171fdd5c763b3538b0c303c48461fa4c1ccd9d)
Risk: Low runtime risk / medium validation risk. The diff is test-only, but the PR’s purpose is to make specific Desktop Playwright flakes deterministic, so a same-head failure in one of those changed specs means the proposed synchronization still does not prove its contract.

Finding

[P2] Navigation tooltip flake fix still fails on the changed exact-head flake proof — desktop/tests/e2e/navigation.spec.ts:704

The PR changes composer Buzz chip labels wrap without orphaning their icons to wait for the sent row ack, wait for the timeline floor to hold for two frames, and require the tooltip to have data-state="open" before asserting the tooltip center is over the current wrapped chip fragment. That is still not sufficient: the exact-head flake check failed this same test on the PR merge commit.

Evidence from Flake Check / Flake check (Playwright smoke, 1/1) for run 41051895661, job 124049928438:
```
Uses: block/buzz/.github/workflows/_ci-flake.yml@refs/pull/8743/merge (b114cdb1d91f85ebf4f540ded08dbbfbbc1973ce)
✘ [smoke] › tests/e2e/navigation.spec.ts:472:1 › composer Buzz chip labels wrap without orphaning their icons
Expected: < 1
Received: 81.3515625
> 704 |       .toBeLessThan(1);
at positionOverFragment (/home/runner/work/buzz/buzz/desktop/tests/e2e/navigation.spec.ts:704:8)
```
This is the exact tooltip-positioning assertion this PR is trying to stabilize. A tooltip can be visible/open while still centered over the previous fragment, so the new data-state="open" assertion does not guarantee useInlineTooltipPosition has processed the pointer-driven fragment reposition. The result is that the advertised flake is still reproducible under the PR’s own repeated smoke run.

Author action: tighten positionOverFragment so each fragment hover deterministically causes the tooltip to reposition over that fragment before the center assertion runs. For example, close/reopen or otherwise force a fresh hover lifecycle per fragment, or wait on an observable that proves the pointer-driven reposition for the target fragment has actually landed. Then rerun the exact-head Playwright flake check and get this changed spec green.

Verification owner: author + CI flake check.

Validation

PASS — git rev-parse HEAD in the review checkout: 13171fdd5c763b3538b0c303c48461fa4c1ccd9d.
PASS — git status --short | wc -l: 0 dirty entries.
PASS — gh api user --jq '.login': jedwards27; live PR author from gh pr view: matt2e.
PASS — gh pr view https://github.com/block/buzz/pull/8743 --json headRefOid,baseRefOid,statusCheckRollup: live head still 13171fdd5c763b3538b0c303c48461fa4c1ccd9d; base 1eb67bb525d66448b56d79f98c4ba0e2188b44c5; Flake Check / Flake check (Playwright smoke, 1/1) is FAILURE.
FAIL — gh run view 41051895661 --job 124049928438 --log-failed: changed navigation.spec.ts:472 failed at navigation.spec.ts:704 with tooltip center delta 81.3515625.
NOT RUN — local Desktop E2E/native/manual. The exact-head repeated CI smoke failure already establishes the author-actionable blocker for this test-only flake-fix PR.

Residual risk: I did not perform native/manual UI validation because this change is test-only and the exact changed automated proof is red. Re-review should start from the next head after the navigation flake proof is fixed.

…rt (#8741) ## Summary Two RunnerTests fixes from the 23–30 Oct flake audit, both in `mobile/ios/RunnerTests/RunnerTests.swift`. Both are test-only. This is one of six PRs split from the reviewed `flakey-tests` branch (siblings below). ### `testLargeTitleTextFadesWithScrollAndCompactTitleCanReverse` (3 runs) - **Runs:** 40748163526 (job 123028155856), 40826294064 (#8679, job 123290415194, passed on attempt 2) and 40921441156 (#8694, job 123617149320), all in Mobile (iOS), attempt 1. None of the branches touches the navigation bar. Signature: `XCTAssertLessThan(visibleOpacity(of: centeredTitle), 0.99)` read 0.9999499, 1.0 and 1.0. - **Cause:** collapsing adds a 0.18 s `CABasicAnimation` on the compact title mask's opacity (`IosNavigationBar.swift` `applyScroll`). The test slept 60 ms and expected the presentation opacity to be mid-fade. The presentation layer follows wall-clock media time. When the Flutter app in the test host keeps the main thread busy, `Task.sleep` resumes after the fade has finished. - **Change:** drop the 60 ms sleep and the mid-fade samples. Right after `scroll(to: boundary)`, which runs the handler synchronously, check that the mask's model opacity is 1. Also check that it carries a `"titleFade"` opacity `CABasicAnimation` from 0 to 1, lasting 0.1–0.5 s. Nothing turns the run loop before the check, so the animation is still attached however long the main thread stalls. After the scroll back, a new `XCTAssertNil` checks that reversing removes the fade. The later 240 ms waits and their end-state checks are unchanged. - **Mutations that should fail it:** - Delete `compactTitleMask.add(fade, forKey: "titleFade")`: the `XCTUnwrap` throws. - Delete `removeAllAnimations()`: the new `XCTAssertNil` fails. The old test missed this. - Set `fade.duration = 0.001`: the band's lower bound fails. ### `testNativeRemovalConfirmationUsesDestructiveAlertAndCancelsOnce` (1 run) - **Run:** 40950548609 (#8433, Dart only, job 123717768224), attempt 1. Signature: `fulfillment(of: [completed], timeout: 3)` expired. - **Cause:** the busy test-host main thread that #8678 handled for other classes. The cancel reply comes from UIKit's dismissal completion, after the dismiss animation runs on that thread. - **Change:** raise the wait to 10 s, matching #8678's `callbackTimeout`. The assertion is unchanged. Dropping `resolve` from the dismissal completion still fails it, and so does resolving before `alert.dismiss`. ### Related issue None found. **Conflicts with #8568** ("Adapt iPhone Duo layouts, rail navigation, and native sheets"). #8568 rewrites the fade test into a loop but keeps the 60 ms sleep and the mid-fade samples. It already conflicts with `main`, and this PR adds `RunnerTests.swift` to its conflicts. #8665 only adds a voice-note test. ### Testing Not compiled against the app or run locally, because Xcode and RunnerTests bog this machine down. `swiftc -parse` accepts the file. The new assertions, copied into a stub `XCTestCase`, typecheck with `swiftc -typecheck` against the iOS simulator SDK and XCTest (Swift 5 mode). The full file needs Flutter and the Buzz module, so it wasn't typechecked as a whole. **The Mobile (iOS) lane is the check.** Pushed with `git push --no-verify`, because the pre-push suites fail when the laptop is under load. ### Readiness An agent review of the combined `flakey-tests` branch (b432453af) found no blockers. `buzz-review-completed` is not added, because the human test step (AGENTS.md "Before opening a PR", step 3) hasn't happened yet. ### Siblings - #8739 ci: Hermit fetch deadline and sccache fallback - #8740 test(relay): thread_window aux-page hold and `api::media` Postgres tests - #8742 fix(desktop): deep-linked message hold (product change) - #8743 test(desktop): four specs racing scroll settles and focus - #8744 test(desktop): five settle classes and remote-owned-mentions 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: Matt Toohey <contact@matttoohey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…kspace (#8744) ## Summary Units 6–9 and 14 of the 23–30 Oct desktop Playwright flake audit, in two commits. The specs now settle before they measure or act, and remote-owned-mentions clears its draft reliably. Everything is test-only. This is one of six PRs split from the reviewed `flakey-tests` branch (siblings below). ### Unit 6: measuring before an animation finishes Each spec now calls `waitForAnimations(page)` before measuring. - `onboarding.spec.ts:1487` (#8715, Integration shard 1; the centring check at :1545 receives 5.13): `showPage("owned")` slides content in from `translateX(48px)` over 650 ms. The spec reads its three boxes in separate `boundingBox` round trips, so they can come from different points of the slide. - `onboarding.spec.ts:2289` (main 40746677244 and 40925172215, and #8666; the spacing check at :2485 receives 4.255): the avatar dialog has a 200 ms zoom-in and a 250 ms height transition. - `projects-v3-screenshots.spec.ts:280`, at :893 (main 39643531998, 40759209995 and 40969909906, plus four runs with fractional menu-edge values): the context rail narrows from 380 to 280 px over 200 ms. ### Unit 7: `fill()` racing a caret move the app makes a frame later - `mention-recipients.spec.ts:376` and `:97` (main 40969965981 and 40969858676): edit mode focuses the end of the composer in a `requestAnimationFrame`. If that frame lands mid-`fill()`, the edit is appended instead of replacing the text. **Change:** use #8682's `replaceComposerText` at both call sites. - `workflow-local-controls.spec.ts:151` (main 40926393897 and 40957616146, and #8239): `selectVariable` restores the caret in a `requestAnimationFrame` after the spec's poll has passed. **Change:** wait two animation frames before filling. ### Unit 8: clicks that hit the wrong element - `profile.spec.ts:1128`, at :1543 (#8523): stacked Sonner success toasts intercept the pointer. **Change:** a local `pressActionRow` helper presses the five action rows with `toBeEnabled`, focus and Enter. - `config-bridge-screenshots.spec.ts:314` (main 40967147375, and #8235): `.last()` resolved while avatar fallbacks were still filling in on 200 ms timers, so it opened nadia's panel instead of Charlie's. **Change:** pick Charlie's row by its text, and check the panel's name before opening Runtime. ### Unit 9: the `createWorkflow` copies (preventive) - `navigation.spec.ts:153` (7 failures on main, none since #8681; 14 first-attempt failures in Smoke shard 7): an unscoped `getByLabel("Message text")` can fill the trigger's filter while `AnimatePresence` keeps it mounted. **Change:** wait for the step inspector, then fill inside it, as `workflows.spec` already does. The wait now lives in one `addSendMessageStep` helper in `tests/helpers/workflows.ts`, which `navigation.spec.ts` and `workflows.spec.ts` (`createWorkflow`, :716, :820) all call. - `workflow-reaction-picker.spec.ts:203-204` is left out. Its Reaction Added trigger has no control labelled "Message text". ### Unit 14 (second commit): `remote-owned-mentions.spec.ts:566` - **Run:** main 40998438103 (Smoke shard 9, job 123877347301). It passed on retry and failed 1 of the 6 attempts it got in the window. `sourceRecord()` at :673 returned thread A's draft instead of null. - **Cause:** on ProseMirror, `fill("")` selects through the DOM, then presses Delete. If ProseMirror hasn't seen the selection yet, it blocks the Delete. Navigating to B then saves A's live text as its draft. This is not a product bug: had the editor really been empty, the cleanup would have cleared A's draft. - **Change:** delete the text with one Backspace per character from the end, then wait for the composer to read empty. The guard assertions are unchanged. ### Related issue None found. Sibling #8743 also edits `navigation.spec.ts`, in a separate hunk. The two merge cleanly in either order. No open PR touches the tests changed here. #6134, #8187, #5778, #8622, #7452, #7812, #8244 and #3342 edit other tests in the same files. ### Testing Not run locally, because Playwright bogs this machine down. Flake Check will repeat the touched specs. `pnpm typecheck` and `pnpm check` pass, and biome's 3 warnings are in untouched files. Ad hoc `tsc` runs over the touched specs and the helper found the same pre-existing errors as on their `main` copies. Pushed with `git push --no-verify`, because the pre-push suites fail when the laptop is under load. ### Readiness An agent review of the combined `flakey-tests` branch (b432453af) found no blockers. `buzz-review-completed` is not added, because the human test step (AGENTS.md "Before opening a PR", step 3) hasn't happened yet. ### Siblings - #8739 ci: Hermit fetch deadline and sccache fallback - #8740 test(relay): thread_window aux-page hold and `api::media` Postgres tests - #8741 test(mobile): RunnerTests title fade and alert wait - #8742 fix(desktop): deep-linked message hold (product change) - #8743 test(desktop): four specs racing scroll settles and focus 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Matt Toohey <contact@matttoohey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

) ## Summary Two CI-workflow fixes from the 23–30 Oct flake audit. This is one of six PRs split from the reviewed `flakey-tests` branch (siblings below). Each PR applies on its own to `main`. ### Hermit tool downloads (5 runs, 1 on main) - **Runs:** 40635610550 and 40941660945, in Detect Changed Paths (`node`). The selection step printed nothing for 9–10 min, the job hit its cap, and every gate failed as cancelled. Three more, 40373404267 on main (PostgreSQL Tests and Desktop E2E Integration 1/3, `pgschema`), 40373003333 (Mobile Android, `cmake`) and 40373467575 (Desktop Build macOS, `just`), got 504s during GitHub's release-asset outage on 10-26, ~17:54–18:00 UTC. - **Cause:** jobs start with an empty Hermit cache, so a tool's first call downloads it, with no deadline. Hermit v0.54.1 tries three times, a second apart, then gives up. - **Change:** a new `scripts/ci-hermit-retry.sh` runs a no-op tool command with a 90 s deadline per attempt, three attempts and 15 s × n backoff. The deadline is plain bash: job control gives each attempt its own process group, which gets TERM and then KILL. macOS runners have no `timeout(1)` and may run bash 3.2. A "Fetch Hermit tools" step calls it for: - `node` and `just` in Detect Changed Paths, where one stall cancels every gate. One `sh -c` invocation covers both, so the worst case is 345 s, inside the 10-minute cap. Two invocations would take 690 s. - `pgschema` in PostgreSQL Tests, Desktop E2E Integration and Backend Integration (via `--help`, since it has no `--version`). - `just` and `cmake` in the Android lane. - `just` in Desktop Build (macOS). The test, `scripts/ci-hermit-retry.test.mjs`, joins Detect Changed Paths' `node --test` list, and the script joins the rust and mobile path filters. One stalled attempt costs ~105 s, which fits every job's cap. - A killed attempt doesn't break the retry. Hermit downloads to a temp file and unpacks to a temp dir, and renames each into place only once it's complete. Its lock is a kernel flock. ### sccache storage failures (2 runs) - **Runs:** 40355289475 (Desktop E2E Relay postgres-tests, 10-26, "Egress is over the account limit") and 40714034945 (relay-binaries, 10-28, "send http request"). - **Cause:** the sccache server checks its GHA cache storage at startup and won't start if that fails. Cargo's first `sccache rustc -vV` spawns it, so the build fails. `SCCACHE_IGNORE_SERVER_IO_ERROR` doesn't help here: in v0.16.0 it is read only when a running server's compile response fails. - **Change:** a "Start sccache" step runs `sccache --start-server`. It outputs `wrapper=sccache`, or an empty wrapper and a warning if the server won't start. The three build steps take `RUSTC_WRAPPER` from it, and cargo treats an empty `RUSTC_WRAPPER` as no wrapper. - The fallback doesn't fail the job later, in sccache-action's post step. At the pinned fc920bf, that step runs `sccache --show-stats` and the JSON form, and fails the job if either exits non-zero. With no server running, v0.16.0's `--show-stats` doesn't start one. It returns zero stats from the client side and exits 0. So the step keeps its stats annotation, and `disable_annotations` stays unset. ### Related issue None found. **Overlaps #8213** ("ci: fix empty root-workspace Rust caches and merge test-unit nextest runs"). #8213 already conflicts with `main`, and this PR adds a conflict in `.github/workflows/ci.yml` (path filters). ### Testing Verified locally: - With a fresh Hermit state dir, `node` was SIGKILLed mid-download, then mid-unpack while holding the lock, then stopped with TERM by the script's own 1 s deadline. Each retry produced a working v24.15.0, at clean-unpack speed. The `sh -c` form fetched both tools, and a 1 s deadline on `sh -c 'sleep 37 && ...'` stopped `sh` and its child, leaving no orphan. Tested under macOS bash 3.2 and Debian bash 5.2. - sccache v0.16.0 (aarch64-apple-darwin) ran against a GHA cache whose `ACTIONS_RESULTS_URL` refused connections, in READ_ONLY and READ_WRITE modes. `--start-server` exited 2 ("Server startup failed: cache storage failed to read"). Both `--show-stats` forms then exited 0, with zero stats and valid JSON. `--stop-server` exited 2, which shows no server had started. Only hosted CI can show: - the script under the runners' real shells, and that healthy runs only pay a few seconds; - whether ~3 min of spaced attempts rides out the next outage. The 10-26 outage lasted ~6 min, longer than this covers; - that the explicit `--start-server` behaves like cargo's implicit start against the real GHA cache. The fallback branch needs a storage outage to run in CI. Not covered here: first fetches of other tools (rustup, uv, pnpm) still have no deadline. A per-job Hermit package cache is the follow-up. Pushed with `git push --no-verify`, because the pre-push suites fail when the laptop is under load. ### Readiness An agent review of the combined `flakey-tests` branch (b432453af) found no blockers. `buzz-review-completed` is not added, because the human test step (AGENTS.md "Before opening a PR", step 3) hasn't happened yet. ### Siblings - #8740 test(relay): thread_window aux-page hold and `api::media` Postgres tests - #8741 test(mobile): RunnerTests title fade and alert wait - #8742 fix(desktop): deep-linked message hold (product change) - #8743 test(desktop): four specs racing scroll settles and focus - #8744 test(desktop): five settle classes and remote-owned-mentions 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: Matt Toohey <contact@matttoohey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

Units 2-5 of the 23-30 Oct desktop Playwright flake audit. All four are test-only. origin/main (1eb67bb, now including #8680) hasn't touched these specs since fae3f03. Of the open PRs, #8622 adds an unrelated test at the end of navigation.spec, and #7812 (stale since 10-06) adds tests elsewhere in three of them. #8680 didn't touch them, but it carried navigation:472 mode A's product half (eb88a98), which is not part of this commit. The code confirms each cause, so none is dropped. navigation.spec.ts:472, "composer Buzz chip labels wrap without orphaning their icons" Runs: 11 jobs in the window, 6 after the earlier fixes, and 4 of the 7 main runs that carry every fix. Run 40970053997 (Smoke shard 7) failed all three attempts. Mode A: jobs 122971493553, 123066839967, 123572467962, 123819180597 and retry 2 of 123784825042. Signature: fragmentStep is null at :634. Cause: rows key on renderKey = localKey ?? id. On main, reconcileChannelWindowMessages keeps only pending sends and thread replies from the cache, so a head refetch or live echo after the ack drops the localKey. The key flips and the row remounts, losing the 220 px width the test set in an earlier evaluate. Change: re-land the test half of closed PR #6852, which never merged. Set the width and measure in one expect.poll, and set the width again before each fragment measurement. Mode B: jobs 123573056202, 123784199542, 123784825042 (twice), 123804428893, 123818728963, 123819543461, and 122924164125 (the Infinity variant). Signature: the |tooltipCenter - cursorX| < 1 poll at :667 receives 81.35 or Infinity. In failing attempt 40970053997 the post-send settle (scrollTop 200, 296, 260, 302) took its last step 21 ms or less before focus, and the tooltip read closed 12 ms after it. In the passing retry 40980513346, scrolling had stopped at least 15 ms before focus. Cause: Radix Tooltip 1.2.16 closes when an ancestor of its trigger scrolls (a capture-phase window listener). Reopening by pointer needs a pointermove while hasPointerMoveOpenedRef is false, then the chip provider's 500 ms delay. Any close clears that timer, and only pointerleave resets the flag. useInlineTooltipPosition moves the content only on pointermove and placement. So a scroll after focus can leave the tooltip closed, or open without the fragment offset, and the spec's single mouse.move never recovers it. Change: before focusing the chip, poll until the timeline sits at its floor (scrollHeight - clientHeight - scrollTop <= 1) at the start of one poll, is still there two animation frames later, and its scrollTop hasn't moved. Waiting only for scrollTop to hold for two frames isn't enough: a timeline whose settle hasn't started yet reads as still, and the failing run's last step landed under two frames before focus. The settle's end state is the floor. useVirtualizedBottomSettle scrolls only when Virtua's ResizeObserver reports a layout change, and after the send and the 220 px wrap the timeline sits short of the floor until the settle catches up. Focusing the chip and moving the pointer over it don't change layout. The send's ack does. It removes the row's "Sending…" status, and the confirmed row can lose its header, since a pending row is never shown as a continuation (MessageRow.tsx:167). The send's bottom intent is still armed, so that re-pins the timeline. So before the floor poll, wait for the sent row's message-send-status to reach count 0. If the ack has already landed, that wait is a no-op. The standalone toBeVisible after focus is gone. positionOverFragment asserts data-state matches /open/ instead, because a closing tooltip stays visible through its exit animation. No retry. Wrapping the measure, move and check in toPass, leaving and re-entering the chip on each attempt, would also pass, but it retries around the race instead of removing it. The ack and floor waits close the scroll window. The only other way to scroll under the tooltip was a remount that drops the row's 220 px width (mode A), and #8680's retainAcknowledgedLocalKeys, on this branch's base (1eb67bb), keeps the row's key. So positionOverFragment is a single pass, as on main, plus mode A's width re-set: set the width, measure, move, assert open, then poll the centre with the default timeouts. huddle-transcription.spec.ts:637, "animates the responding agent with the shared speaker ring" Runs: 9 jobs, always Smoke shard 4 attempt 1. Main: 39896948198, 40718743531, 40732061485, 40840949170, 40906253761, 40969965981 and 40983029157. PRs: #8715, #8666. Signature: toBeFocused() at :697 reads inactive for all 14 polls over 5 s. At +3.0 s in the failure video (40983029157, job 123827818084) the caret is in "Message #huddle". Cause: useComposerAutofocus re-runs when `focus` changes. That's focusEnd, which depends on the editor, so it runs again once the editor mounts. It backs off only for input, textarea, select and contentEditable focus, so it takes focus from the focused trigger. Change: wait for message-input to be focused before focusing the trigger. The same spec already does this at :855. scroll-history.spec.ts:1289, "fast middle-page scroll settles with continuous mounted coverage" Runs: 9 jobs in the window. After the fixes: main 40980404335 (Smoke shard 9, job 123819180518), two attempts on #8720, and the brain/native-account-setup branch. Signature: the viewportCoverage poll expects < 100 and receives 200. The failure screenshot shows the timeline at the floor. The 200 px is the bottom spacer (--composer-overlay-height) under the last row. Cause: TimelineMessageList arms useVirtualizedBottomSettle when the channel first positions. Its ResizeObserver then pins to the floor until listenForReaderScroll input or an accepted target cancels it. handleScroll deliberately doesn't cancel, and a prepend delta doesn't settle, so the intent survives the prepend and the spec's scrollTop writes. Virtua's re-measure after the jump pulls the list back down. Change: before the fast scroll, hover the timeline and wheel up 120 px. Then poll until it is more than 32 px from the floor (the timeline's at-bottom band) and scrollTop holds for two frames, so the writes stay the last scroll. custom-emoji.spec.ts:370, "reacting with a custom emoji renders via the loopback media proxy" Runs: main 40787609859 (10-28), main 40983029157 (Smoke shard 3, a run with every fix), and #8241 (agent and auth files only). Signature: the poll at :453 expects the inline "Add reaction" opacity "0" and receives "1". The error context marks button "Open reactions" [active]. Cause: the non-modal Radix Popover returns focus to its trigger when the picker closes. FocusScope does that in a setTimeout(0) after the content unmounts, and the content unmounts after its 100 ms exit animation. That can land after the spec's blur. The action bar is hidden by opacity only, so the trigger takes focus, and group-focus-within/message keeps the button visible. Change: wait for the "Open reactions" trigger to be focused, then blur. The note suggested waiting for em-emoji-picker to reach count 0. That still leaves the setTimeout window open. Focus reaches the trigger only after unmount, so this wait covers both. Verification Not run locally: the Flake Check lane will repeat the touched specs. pnpm typecheck and pnpm check pass. biome's 3 warnings are in untouched files. An ad hoc tsc ran over the four specs, using the desktop tsconfig with only those files, and over HEAD's copies of them. Both gave the same error counts: navigation 7, huddle 17, scroll-history 0, custom-emoji 2. The messages are identical once line numbers are stripped, and all are pre-existing: no Node types, findLast against the ES2022 lib, and the leadingBounds narrowing at navigation:576. With the floor wait in place and the retry dropped, navigation still gives the same 7. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Matt Toohey <contact@matttoohey.com>

…ring Follow-up to the 10-30 review of #8743 on 13171fd. "composer Buzz chip labels wrap without orphaning their icons" still failed the PR's Flake Check: run 41051895661, job 124049928438, 1 of 10 repeats. The centre poll in positionOverFragment expected < 1 and received 81.3515625. The caller was :711 of the merge commit, positionOverFragment(0), so this was the first fragment. The current head (832737e, a rebase) has the same positionOverFragment. Evidence: the tooltip is open. data-state matches /open/, and the error context still marks the chip [active]. The screenshot has the tooltip at x 333-621, centre 477. That's the centre of the whole two-line chip, where Radix places the tooltip when focus opens it. The cursor was at 395.6, over the "relay" fragment. In the video the timeline stops moving before the tooltip fades in at that spot, and the tooltip doesn't move for the rest of the run. Cause: useInlineTooltipPosition moves the content only from the trigger's pointermove. Once a pointermove lands, the hook positions the content in that frame or the next, and later Radix placements re-apply the offset. So with the pointer still, the tooltip stays at its focus placement only if the spec's move never reached the chip. Virtua 0.49.3 causes that. While the list is scrolling, its Virtualizer sets pointer-events: none on the item container. A 150 ms timer clears it, and every scroll event restarts the timer. Scrolls Virtua makes itself, like the bottom settle's scrollToIndex, don't set the flag, but other scroll writes can. The artifacts don't show which one set it here. The floor wait only proves scrollTop held for two frames, about 33 ms. A move inside the window hit-tests past the rows. When the rows take pointer events again the pointer hasn't moved, so no pointermove follows, and in this run none did. data-state can't catch this, because focus already opened the tooltip. Fix: positionOverFragment measures the fragment and hit-tests its centre with document.elementFromPoint in one evaluate. It polls until that point lands on the chip, then moves there. elementFromPoint skips pointer-events: none, so the poll waits out Virtua's flag. After the ack and floor waits nothing scrolls, so the move reaches the chip, and the centre poll then proves the reposition landed. This waits on a precondition. It doesn't retry the hover: the move, the open check and the centre poll each still run once per fragment. A fresh hover per fragment wouldn't fix this alone, because a re-entry inside the window misses the chip the same way. Not a product change: a real pointer sends a stream of moves, so the next one after the window positions the tooltip. Verification: pnpm typecheck and pnpm check pass, with biome's 3 existing warnings. An ad hoc tsc over navigation.spec.ts with the desktop tsconfig gives the same 7 pre-existing errors, none in the changed lines. Playwright wasn't run locally. The Flake Check lane will repeat the spec. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Matt Toohey <contact@matttoohey.com>

matt2e · 2026-11-02T12:26:40Z

🤖 Addressed the P2 finding in the 10-30 review in 3b10292.

The failure was on the first fragment. The tooltip was open, but still where focus had placed it (centred on the whole chip, x 477), because the hover's pointermove never reached the chip. Virtua 0.49.3 sets pointer-events: none on timeline rows until 150 ms after the last scroll event, which is longer than the floor wait's two frames. Once the rows take pointer events again, a still pointer gets no new pointermove.

positionOverFragment now polls until the fragment's centre hit-tests to the chip (document.elementFromPoint) before its single move. So the centre assertion only runs after a pointer event has reached the target fragment. The move, the open check and the centre poll still run once per fragment, with no retry. Flake Check on the new head will confirm it.

wesbillman

🤖 Carl, an automated reviewer, commenting via Wes's GitHub account.

Verdict: no blockers at 3b102926b40eccfa555ec0a397e9792ed461aa08. Test-only; reviewed solo.

What I checked

Each fix targets a mechanism that exists in source: useComposerAutofocus only defers to an already-focused text surface, so a focused button loses to it (huddle); the "Open reactions" popover in MessageActionBar.tsx has no onCloseAutoFocus override, so Radix does return focus to the trigger (custom-emoji); useVirtualizedBottomSettle cancels on non-Ctrl wheel but not on scrollTop writes (scroll-history); Virtua 0.49.3 sets pointerEvents: "none" on items while scrolling with a 150 ms settle timer (navigation hit-test wait).
Exact-head Flake Check (run 41444636305, job 125274890906): --repeat-each=10 --retries=0, 40/40 passed across all four touched specs. This clears the navigation.spec.ts:704 failure from the earlier review on 13171fd.
No assertion was weakened. Each change adds a wait for a real precondition, and none retries around the asserted behavior.

Optional

The PR body's Mode B section predates 3b10292. It doesn't mention the Virtua pointer-events cause or the hit-test wait in positionOverFragment, and "There is no retry loop around the race" now reads oddly beside that new poll. Worth a one-paragraph refresh.
Readiness is still pending the human test step from AGENTS.md, as the body notes.

…ests (#8740) ## Summary Two buzz-relay test fixes from the 23–30 Oct flake audit. Both are test-only. This is one of six PRs split from the reviewed `flakey-tests` branch (siblings below). ### `thread_window_bridge_restarts_both_aux_hops_after_replica_failure` (3 runs) - **Runs:** 40799617319, 40924179886 and 40930100994 (#8697, docs only), all on 10-29 in PostgreSQL Tests, attempt 1 (jobs 123208043033, 123632125866, 123651641392). None of the branches touches thread_window, and each run passed on a re-run. Signature: `failure_postgres_tests.rs:46`, "barrier must precede closure completion", left: 2, right: 1. - **Cause:** `pause_after_aux_page` polls the request until a `thread_window_aux` span closes, then expects exactly one. The fixture's 1,001 reactions make two replica pages at `AUX_LIMIT` 1000, and each page is one round trip on the transaction already held. A loaded runner can deschedule the test thread after page 2's query is written. Postgres then answers first, and the same poll reads page 2 too. - **Change:** `test_support` gains a `PausingProxy`, a trimmed copy of buzz-db's private one with only the hold-everything switch. The replica reader pool connects through it. `AuxPages` pauses it when the first aux span closes. That runs inside the request's poll, after page 1's response is consumed and before page 2's query is written, so page 2 stays pending however fast Postgres answers. The test resumes the proxy after it terminates the reader's backend. The held page then sees the termination, and the closure restarts on the writer, as before. The other three `pause_after_aux_page` callers read from the writer and pass `None`. ### `api::media` tests that need Postgres (fail every time Flake Check selects them) - **Run:** 40954304982 (#8658), 10-29, Flake check (Rust), job 123730434146. All six `test_state()` tests panic at the community-seed `expect` after the 30 s sqlx acquire timeout. - **Cause:** when a hunk lands outside a test body, Flake Check selects every test in the file. It skips only `postgres_tests::`, `postgres_*` binaries and `external_infra`, and its job has no database. These six tests seed `relay.example` through Postgres but sat in plain `mod tests` without `#[ignore]`. So any PR that changes non-test code in `media.rs` fails that lane, and at least 8 open PRs touch the file. No other lane ran these tests either. - **Change:** move `test_state`, the `media_get_*` helpers, `media_request` and the six tests into `tests::postgres_tests`. Mark each test `#[ignore = "requires Postgres"]`, and point `test_state` at `test_support::database_url()`, as the module's other states do. The PostgreSQL lane now runs them, and Flake Check skips them. The change also drops imports `mod tests` no longer uses, and updates the Justfile comment that gave `api::media` as the reason the infra-free lane is scoped to `api::admin`. - When `media.rs` is staged, the pre-commit secret scan reads the whole file and flags the module's existing public ES256 test key (`TEST_EC_PKCS8_PEM`). The key is now written on one line with a sadscan marker, as `invites.rs` already does. Its bytes are unchanged. ### Related issue None found. **Conflicts with #8451 and #8444**, which both already conflict with `main`. The one-line `TEST_EC_PKCS8_PEM` rewrite is the only new conflict hunk with each. The test move merges cleanly with both. ### Testing Verified locally: - Each of the four `pause_after_aux_page` tests passes when run alone against local Postgres through `scripts/postgres-test-run.sh`. - A forced check, not committed: after the barrier, the test gave page 2 another 500 ms over ten re-polls and asserted the page count stayed at 1. It passed with the pause and failed with `None`, with the CI signature (left: 2, right: 1). A true same-poll burst needs the OS to preempt between sqlx's write and read, so it was not forced directly. - `check-postgres-test-discovery.py` accepts the touched files and all 621 files under `crates/`, and `scripts/test-postgres-test-discovery.sh` passes. Each of the six media tests passes when run alone against local Postgres. - `cargo fmt --check` and `cargo clippy -p buzz-relay --all-targets -- -D warnings` are clean under 1.98.1. Only hosted CI can show the full lanes, which were not run locally. The six media tests have never run in CI, so this PR's PostgreSQL lane is their first hosted run. Pushed with `git push --no-verify`, because the pre-push suites fail when the laptop is under load. ### Readiness An agent review of the combined `flakey-tests` branch (b432453af) found no blockers. `buzz-review-completed` is not added, because the human test step (AGENTS.md "Before opening a PR", step 3) hasn't happened yet. ### Siblings - #8739 ci: Hermit fetch deadline and sccache fallback - #8741 test(mobile): RunnerTests title fade and alert wait - #8742 fix(desktop): deep-linked message hold (product change) - #8743 test(desktop): four specs racing scroll settles and focus - #8744 test(desktop): five settle classes and remote-owned-mentions 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: Matt Toohey <contact@matttoohey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

…r-grants * origin/main: (191 commits) fix(relay): refuse a second listed open channel with the same name (#8782) docs(nip-fa): make assertion lifetime issuer operator policy (#8934) fix(mobile): open the public Builderlab login the iOS bridge allows (#8914) fix(desktop): skip a starter channel the relay will never create (#8911) fix(mobile): hide the Flutter debug banner (#8915) mobile: keep a thumbnail fallback apart from a direct load of the same URL (#8913) fix(mobile): prompt Builderlab sign-in instead of labeling agents desktop-only (#8907) feat(mobile): add Buzzies and refresh agent avatar picker (#8921) fix(deps): clear RUSTSEC-2026-0433 and RUSTSEC-2026-0429 from the dependency policy (#8922) test(relay): hold the replica's second aux page and move media's DB tests (#8740) test(desktop): stop four E2E specs racing scroll settles and focus (#8743) fix(mobile): catch up unread from the newest message already seen (#8901) fix(mobile): resync read state from the last fetch, not the whole week (#8903) fix(mobile): show remote agent instructions from the registry (#8908) feat(mobile): show NIP-FI verified names (#8858) fix(mobile): keep community icons on originals and record thumbnail 404s at fetch (#8896) chore(mobile): delete dead code with no remaining UI path (#8880) fix(mobile): let slow image downloads finish (#8881) fix(mobile): show Bestie as a continuous conversation (#8890) fix(mobile): keep mention rows still and cache directory searches (#8875) ... Signed-off-by: Philip Azar <pazar@squareup.com>

## Summary A product fix for the most frequent unfixed desktop E2E flake, `message-target-highlight.spec.ts:79`. A deep-linked message now holds its place against bottom settles until the reader scrolls. This is one of six PRs split from the reviewed `flakey-tests` branch (siblings below). - **Runs:** it failed in all 7 main runs whose SHA carries every earlier flake fix (40969965981, 40970005965, 40970053997, 40980258899, 40980404335, 40980513346, 40983029157). It also failed in 26 jobs since those fixes landed, on main and on PRs #8235, #8239, #8241, #8666 and #8680. Only the two cases that pick `mounted[2]` fail: "same channel, row loaded off screen" (15 jobs) and "other channel, row further up" (11 jobs). The target scrolls in and flashes, then the timeline lands on the newest message. `stillOnScreen` at :179 reads false (twice it was `flashedOnScreen` at :153). ### Cause The failure videos (run 40983029157, Smoke shard 6) show that the thread panel opening is a precondition, not the trigger. A later floor report moved the target: `TimelineMessageList`'s `onScroll` reported within 32 px of the bottom, during or after the older-page load that only a `mounted[2]` target sets off. `onVirtualizerAtBottomStateChange(true)` reset the anchor to at-bottom. Then the split-panel settle, the viewport-resize settle or the next append settle pinned the timeline to the floor. Which Virtua layout pass emits the floor report is still unidentified. ### Change Accepting a virtual route target sets `targetHoldRef` in `useAnchoredScroll`. Only the two `targetMessageId` paths set it, via `holdTarget`. The public `scrollToMessage`, which the oldest-unread pill and find-in-channel use, doesn't hold, and it replaces any earlier hold. While the hold is set: - The split-panel and viewport-resize settles are skipped. - A floor report still updates `isAtBottom` and the new-message count, but keeps the message anchor, so live appends don't settle either. - A commit that changes the newest message sets `isAtBottom` false and clears `virtualizerAtBottomRef`. It adds the rows after the previous newest one to the new-message count. So the "Jump to latest" / "N new messages" pill still appears for rows below the fold (Review-Proven Rule 6). A history page that fills the gap below a cold target raises no pill, and neither does deleting the newest message. - Viewport reflow re-centres the target through `virtualScrollToMessage`. It runs from the resize observer and when the split panel opens or closes. The hold is released by reader scroll input: a wheel, a touch drag, a pointerdown on the scroller itself, or a scroll key. Those listeners already cancel bottom intent in `useVirtualizedBottomSettle`, and this PR shares them as `listenForReaderScroll`. Jump to latest, the reader's own send and a channel change also release it. A release at the floor restores the at-bottom anchor, so the timeline follows live messages again. `onTargetReached` does not release the hold. ### Known limits - Programmatic scrolls (focus moves, `scrollTop` writes) don't release the hold, but a find or unread-pill jump replaces it. A resize after such a scroll re-centres the target. - ChannelPane's composer-height settle still calls `scrollToBottom` within 32 px of the floor, which releases the hold. - Live messages that arrive under a hold near the floor aren't followed until reader input, Jump to latest or the reader's own send. The pill shows them, with their count. - Under the hold, only rows after the previous newest message count. A same-second row that sorts just ahead of it raises no pill until a later row lands. - Agent review raised two optional gaps, and scrolling recovers from both: - If the previous newest message is deleted and a new row arrives in the same deferred commit, 0 rows are counted. - A thread reply sent with "also send to channel" doesn't arm the bottom intent, so it shows as "1 new message" instead of being followed. ### Related issue None found. ### Testing `useAnchoredScroll.lifecycle.test.mjs` replays the CI sequence: accept a route target, clear it, open the split panel, report the floor, resize and append a live message. It asserts no bottom settle, a re-centre on the panel opening and on the resize, and the pill on the append. Further cases cover: - each release path; - a find jump on a held timeline; - a descendant pointerdown keeping the hold; - a gap-fill page and deleting the newest message, neither of which raises the pill. The split-panel and viewport-resize policy tables each gain a held row. Mutations were run over the lifecycle file and both policy tables (29 tests, all pass intact). Each of the 20 mutations fails at least one test: | Mutation | Tests that fail | |---|---| | Hold never set (the old behaviour) | 12 | | Split-panel settle ignores the hold | 13 | | Viewport-resize settle ignores the hold | 13 | | Floor report resets a held anchor | 12 | | No split-panel re-centre | 12 | | No viewport-resize re-centre | 12 | | Reader input doesn't release the hold | 6 | | Held append raises no pill | 2 | The commit message lists the other 12, each failing 1 or 2 tests. `pnpm typecheck` and `pnpm check` pass. All 46 tests in the files that import the touched modules pass. Only hosted CI can show whether the spec now holds in Smoke shard 6 and in Flake Check's repeats, because Playwright was not run locally. It also has to show that `scroll-history.spec.ts` and the other timeline specs keep bottom-follow working. Pushed with `git push --no-verify`, because the pre-push suites fail when the laptop is under load. ### Readiness and human check An agent review of the combined `flakey-tests` branch (b432453af) found no blockers. This changes desktop app behaviour, so it needs a human in-app check before `buzz-review-completed` is added. Suggested check, in `just dev` against a channel with a few pages of history: 1. Open a message link (a mention or search hit) to a message several screens up, once in the same channel and once from another channel. The message should flash and stay on screen after older history loads, including when the thread panel opens or closes, or the window is resized. 2. With the target still held, have someone post in the channel. The timeline stays put, and the pill reads "1 new message". 3. Wheel-scroll to the bottom, or click Jump to latest. The next message that arrives is followed. ### Siblings - #8739 ci: Hermit fetch deadline and sccache fallback - #8740 test(relay): thread_window aux-page hold and `api::media` Postgres tests - #8741 test(mobile): RunnerTests title fade and alert wait - #8743 test(desktop): four specs racing scroll settles and focus - #8744 test(desktop): five settle classes and remote-owned-mentions 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Signed-off-by: Matt Toohey <contact@matttoohey.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

matt2e requested a review from a team as a code owner October 30, 2026 11:58

matt2e temporarily deployed to codex-review October 30, 2026 11:58 — with GitHub Actions Inactive

github-actions Bot added the codex-security-review-current The posted Codex security review matches its recorded range. label Oct 30, 2026

jedwards27 reviewed Oct 30, 2026

View reviewed changes

matt2e force-pushed the flakey-tests-desktop-e2e-scroll-focus branch from 13171fd to 832737e Compare November 2, 2026 03:19

github-actions Bot removed the codex-security-review-current The posted Codex security review matches its recorded range. label Nov 2, 2026

matt2e temporarily deployed to codex-review November 2, 2026 03:19 — with GitHub Actions Inactive

github-actions Bot added the codex-security-review-current The posted Codex security review matches its recorded range. label Nov 2, 2026

github-actions Bot removed the codex-security-review-current The posted Codex security review matches its recorded range. label Nov 2, 2026

matt2e temporarily deployed to codex-review November 2, 2026 12:26 — with GitHub Actions Inactive

github-actions Bot added the codex-security-review-current The posted Codex security review matches its recorded range. label Nov 2, 2026

wesbillman reviewed Nov 2, 2026

View reviewed changes

wesbillman approved these changes Nov 2, 2026

View reviewed changes

wesbillman merged commit a83926d into main Nov 2, 2026
73 checks passed

wesbillman deleted the flakey-tests-desktop-e2e-scroll-focus branch November 2, 2026 15:28

Navigation Menu

Repository navigation

test(desktop): stop four E2E specs racing scroll settles and focus - #8743

test(desktop): stop four E2E specs racing scroll settles and focus#8743
wesbillman merged 2 commits into
mainfrom
flakey-tests-desktop-e2e-scroll-focus

matt2e commented Oct 30, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Oct 30, 2026 •

edited

Loading

Uh oh!

jedwards27 left a comment

Uh oh!

matt2e commented Nov 2, 2026

Uh oh!

wesbillman left a comment

Uh oh!

Uh oh!

This branch was previously deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

matt2e commented Oct 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

navigation.spec.ts:472 "composer Buzz chip labels wrap without orphaning their icons"

huddle-transcription.spec.ts:637 "animates the responding agent with the shared speaker ring"

scroll-history.spec.ts:1289 "fast middle-page scroll settles with continuous mounted coverage"

custom-emoji.spec.ts:370 "reacting with a custom emoji renders via the loopback media proxy"

Related issue

Testing

Readiness

Siblings

Uh oh!

github-actions Bot commented Oct 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔐 Codex Security Review

Review Summary

Findings

Notes

Uh oh!

jedwards27 left a comment

Choose a reason for hiding this comment

Finding

Validation

Uh oh!

matt2e commented Nov 2, 2026

Uh oh!

wesbillman left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

This branch was previously deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

matt2e commented Oct 30, 2026 •

edited

Loading

`navigation.spec.ts:472` "composer Buzz chip labels wrap without orphaning their icons"

`huddle-transcription.spec.ts:637` "animates the responding agent with the shared speaker ring"

`scroll-history.spec.ts:1289` "fast middle-page scroll settles with continuous mounted coverage"

`custom-emoji.spec.ts:370` "reacting with a custom emoji renders via the loopback media proxy"

github-actions Bot commented Oct 30, 2026 •

edited

Loading