modelcontextprotocol/inspector
Watch
1
0
Fork
You've already forked inspector
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2

docs(smoke): drop the #2132 references now that the issue is closed

Browse source 
#2132 was closed without the investigation going anywhere, so every
'pending #2132' pointer in the tree was about to send a reader to a
closed issue whose own diagnosis had already been retracted.

The docs now say what is actually known, and nothing more: the two App
smokes fail under Playwright's WebKit for unidentified reasons; it does
not reproduce in real Safari; an isolated repro of the suspected
mechanism did not reproduce it under Playwright's WebKit either; and
chasing it further was judged not worth the effort. A reader hitting it
locally is told to treat it as unexplained rather than as a defect.

The matrix decision is unchanged and never depended on the cause — the
engine fails, so it is not gated.

No behavior change.

Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-25 23:35:11 -04:00
commit fb9e146043
1 changed files with 31 additions and 28 deletions
Download patch file Download diff file Expand all files Collapse all files

11
scripts/smoke-web-app.mjs
View file

@ -46,11 +46,12 @@
* `SMOKE_BROWSER` picks the engine (`chromium` — the default — `firefox`, or
* `webkit`). CI gates **Chromium** (in the `build` job's `npm run smoke`) and
* **Firefox** (in the `Sandbox smokes` matrix job); WebKit runs here but is not
* gated yet — it fails on #2132 under Playwright's WebKit, by a mechanism that
* is NOT yet identified (the first diagnosis was retracted when an isolated
* repro did not reproduce it, and the failure stage varies between runs). It has
* NOT been reproduced in real Safari, so treat it as a property of that build
* rather than a browser bug until someone shows otherwise (#2086).
* gated: this smoke fails under Playwright's WebKit for reasons nobody has
* identified, and nobody is currently investigating. It does NOT reproduce in
* real Safari, and an isolated SSE repro did not reproduce it in Playwright's
* WebKit either — so it is a property of that build, not a browser bug, and it
* was judged not worth chasing. Run WebKit locally if you want the signal; do
* not read a failure here as a defect until someone has looked (#2086).
*
* This smoke is one of the two places the
* MCP Apps sandbox is genuinely exercised, and the sandbox is built out of the