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

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

14
.github/workflows/main.yml vendored
View file

@ -127,9 +127,8 @@ jobs:
# there plus whatever the matrix below names.
#
# This is the only place the MCP Apps sandbox is exercised on a non-Chromium
# engine, and it earned its keep immediately: pointing the smokes at WebKit is
# what found #2132, an undelivered-SSE-tail hang no Chromium-only tier could
# see. (Note #2132 is NOT known to affect Safari — see the matrix comment.)
# engine — which is why Firefox is gated here rather than assumed to behave
# like Chromium.
#
# The unit tests cannot substitute — `sandbox-csp.test.ts` asserts
# which policy STRING is built, which passes identically on an engine that
@ -149,10 +148,11 @@ jobs:
matrix:
# `webkit` belongs here and is deliberately absent: the smokes RUN in it
# (`SMOKE_BROWSER=webkit` works, and smoke:web:browser passes), but the
# two App smokes fail on #2132, by a mechanism not yet identified — the
# first diagnosis was retracted when an isolated repro did not reproduce
# it. Not reproduced in real Safari either, so read it as a property of
# Playwright's WebKit build rather than a browser bug. Adding it here is a one-word diff once it is
# two App smokes fail there for reasons nobody has identified. It does
# NOT reproduce in real Safari, and an isolated SSE repro did not
# reproduce it under Playwright's WebKit either, so it reads as a
# property of that build rather than a browser bug — and chasing it
# further was judged not worth the effort. Adding it here is a one-word diff once it is
# resolved. An engine is either green or absent; a `continue-on-error`
# job would report coverage nobody is holding to a standard.
browser: [firefox]