Daniel Han fdf7f94f46 ci(mac): single-process Chromium + JSON.parse try/catch in pipeTransport ... Run 25491698868 / job 74801076186 hit the Playwright pipeTransport 'Unexpected end of JSON input' crash on ALL THREE retry attempts (at 11:00:52, 11:01:07, 11:01:21 — only ~15s apart). The retry-with- Studio-reset wrapper from d35bf6a couldn't recover because the crash hits 100% of attempts on this run, not as a rare race. Two complementary fixes: 1. tests/studio/playwright_chat_ui.py + playwright_extra_ui.py: pass --single-process / --no-sandbox / --disable-dev-shm-usage / --disable-gpu to chromium.launch. --single-process is the key one: it keeps the renderer in the browser process, eliminating the browser↔renderer IPC pipe that was the actual crash site (Chromium's renderer was dying mid-startup and corrupting the pipe stream the Node driver was parsing). 2. .github/workflows/studio-mac-ui-smoke.yml: backport upstream Playwright's try/catch around the two JSON.parse(message) sites in driver/.../pipeTransport.js so a malformed stdout chunk (e.g. empty buffer between two \0 delimiters) is dropped silently instead of throwing and killing the entire Node driver. Newer Playwright versions ship this guard upstream; we patch it in via a python script after `playwright install chromium` so the fix lives only in CI's Mac job. Idempotent: prints "no matches; skipping" if upstream changes the pattern. The retry loop from d35bf6a is kept as a third line of defense for any residual Chromium-died-and-stayed-dead scenarios.		2026-05-07 11:05:32 +00:00
..
ISSUE_TEMPLATE	Update issue template	2026-03-23 10:10:15 +05:30
workflows	ci(mac): single-process Chromium + JSON.parse try/catch in pipeTransport	2026-05-07 11:05:32 +00:00
CODEOWNERS	Update CODEOWNERS	2026-03-13 13:38:19 -07:00
dependabot.yml	CI(security): defense-in-depth additions across 7 axes	2026-05-07 00:09:40 +00:00
FUNDING.yml	Update FUNDING.yml (#3792)	2025-12-28 19:57:43 -08:00