Repository navigation
fix(terminal): allow Windows paste shortcuts - #5485
Open
Glucksberg wants to merge 2 commits into
Open
Glucksberg wants to merge 2 commits into
Glucksberg wants to merge 2 commits into
Conversation
added 2 commits
August 10, 2026 12:05
Signed-off-by: Glucksberg <[email protected]>
Signed-off-by: Glucksberg <[email protected]>
Glucksberg
marked this pull request as ready for review
August 10, 2026 18:56
matt2e
added a commit
that referenced
this pull request
Nov 14, 2026
… closes (#9440) ## Summary `desktop/src/features/terminal/TerminalSubstrate.test.mjs` can pass every test and then run the Desktop JS job out of memory several minutes later. This moves the React Testing Library unmount from `beforeEach` to `afterEach`, so no tree is still mounted when the jsdom window closes. Only the test file changes (6 insertions, 2 deletions). Commit (cherry-picked unchanged from a local flake-fix series): - `test(desktop): unmount every TerminalSubstrate tree before the window closes` ### CI sighting One sighting was found in the CI runs from 7 to 12 November 2026 that were searched: - 9 November 2026, "Desktop Domain / Desktop JS", run 42706004493 attempt 1 (on #9227; the rerun passed): - https://github.com/block/buzz/actions/runs/42706004493/job/129463488242 In that job the suite reported 6,950 of 6,951 passing. The log shows `An update to TerminalSubstrate inside a test was not wrapped in act(...)` at 21:54:33Z, then `FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory` at 22:02:17Z, and the file is reported as failed at file level (`test at src/features/terminal/TerminalSubstrate.test.mjs:1:1`) after 504.6 s. ### Root cause The file called `cleanup()` only in `beforeEach`, so the last test's tree was still mounted when `after(() => dom.window.close())` ran. If ThemeProvider's asynchronous palette update landed after that close, it re-rendered the substrate, the splash effect's palette guard passed, and `requestAnimationFrame` on the closed window started a fresh jsdom interval that nothing cleared. That 60 Hz loop repainted the banner into the test's recording `getContext` stub indefinitely, and `paintLog` grew until the heap limit. No individual test hangs, so a per-test timeout would not catch it. ### Fix `afterEach(() => cleanup?.())` unmounts every tree, including the last, before `after()` closes the window. The `beforeEach` call became redundant and is removed. No assertions change, and no timeouts, retries or sleeps are added. ### Related issue N/A (flake fix). No existing issue or PR for this failure was found. Three open PRs touch the same test file (#5057, #5485, #7777); none of them changes where `cleanup` runs. ### Testing Human testing is still required. This PR does not carry `buzz-review-completed`; the author has not yet run this test themselves on this branch. #### Verification of the fix (before this branch was split out) - The test file, 5 consecutive runs: 25 of 25 tests passed each time in about 6.8 s, with no `act` warning. - The CI out-of-memory failure was not reproduced with the real test file. Its mechanism was reproduced in a scratch harness with the same stubs: without cleanup before the window close, 3 of 3 runs left the palette unresolved at close, added 11,556 `paintLog` entries per 100 ms, kept one live timer, and never exited. With cleanup before the close, 3 of 3 runs added no entries, left no timers, and exited on their own. #### Local checks on this branch The push ran the repository's full pre-push hook set from a checkout of this branch's head (`7f4117340`), with no lanes excluded and without `--no-verify`. The branch is one commit behind `main`; that commit changes only mobile and docs files, none of them touched here. Ran and passed: - `branch-skew`, `push-head-scope` and `file-size-check` - `desktop-check` (`pnpm check`) - `desktop-typecheck` (`pnpm typecheck`) - `desktop-test` (`pnpm test`, the full desktop unit suite, which includes `TerminalSubstrate.test.mjs`) Did not run: - `rust-tests`, `desktop-tauri-checks` and `mobile-checks`. The hook selects lanes by changed path, and this branch changes no Rust, Tauri or mobile file. - Desktop builds and the Playwright E2E suites, which are CI-only. - `just ci`. - The 5-run repetition and the scratch harness above were not repeated on this branch. A green run does not prove the flake is gone: the failure needs the palette update to land after the window closes. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Signed-off-by: mtoohey <[email protected]> Signed-off-by: Matt Toohey <[email protected]> Co-authored-by: Claude Fable 5.1 <[email protected]>
This branch has not been deployed
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.
Problem
Buzz Term encoded both
Ctrl+VandCtrl+Shift+Vas the^Vcontrol byte on Windows, then calledpreventDefault(). That prevented WebView2 from delivering the clipboard payload to the terminal's existing paste handler.Implementation
Ctrl+VandCtrl+Shift+Von Windows.Cmd+Von macOS andCtrl+Shift+Von Linux, while LinuxCtrl+Vremains Readline quoted-insert.event.keyso alternate keyboard layouts work, and reject Alt/mixed-modifier chords.onPastepath, including bracketed-paste wrapping.This is a focused follow-up discovered while field-testing #5425 / #4930. It is not a duplicate: #5425 fixes native PTY spawn, teardown, and PATH behavior; this PR fixes frontend keyboard event routing. I searched open PRs and issues for the Windows paste shortcuts and found no existing report or patch.
Tests
^V, and paste exactly once through bracketed paste.Ctrl+Vstill sends^V, whileCtrl+Shift+Vwaits for the paste event and forwards the clipboard exactly once through bracketed paste.just cicomponent set passed. The aggregate invocation was interrupted during Tauri compilation only because the isolated worktree filled the host disk; after removing its regenerable roottarget/,just desktop-tauri-testandjust mobile-testboth passed. Notable totals: 2,383 Tauri app tests passed (14 environment-dependent tests ignored), terminal crate suites passed, and 1,261 Flutter tests passed.pnpm check, desktop typecheck, Rust fmt/clippy/check, web check/build, andgit diff --checkpassed. The frontend check reports one warning and two informational findings already present on currentmain, outside these files.Windows field proof
The exact patch was built and tested on Windows 11 before being cleanly rebased onto current
main(the canary commit and the production-code commit in this PR have the same stable patch ID).b00790a6ceb4cb0967fe07711d7174338cd92f8dBuzz_0.5.9-fork.8_x64-setup.exe049a0507694002af0f7232c3158f5915f0536fd9e260f506075404023695f4efCtrl+VandCtrl+Shift+Vpaste once without emitting^V. In shells with bracketed paste enabled, the temporary active-region emphasis clears on the next keypress as expected.Manual test
Ctrl+V; confirm it appears once and no^Vis inserted.Ctrl+Shift+V.Visual evidence
No screenshot is included because this changes keyboard event routing and has no persistent visual state. The Windows canary run and manual interaction results above are the relevant behavioral evidence.
Deferred work
None for this fix.