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): retract the #2132 mechanism claim; state that it is unknown

Browse source 
An isolated repro of the mechanism I described — a server writing three
SSE frames then going silent with the connection held open, read via
fetch + getReader — delivers every frame in all three engines, WebKit
included. So 'the SSE stream's last message is not delivered' is not a
supported description of the failure.

The keep-alive experiment that appeared to confirm it was one
observation, and the failure is not even stable in shape: two consecutive
webkit runs failed at different stages (ready wait vs connect wait),
which a deterministic buffering bug would not do.

What is unchanged: the App smokes really do fail under Playwright's
WebKit, which is why the engine stays out of the matrix; that reason
never depended on the mechanism. The parseSSE cross-chunk defect also
stands, being read off the code rather than inferred from an experiment.

No behavior change.

Signed-off-by: cliffhall <cliff@futurescale.com>
This commit is contained in:
cliffhall 2026-08-25 23:02:43 -04:00
commit d493b232b3
1 changed files with 16 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -149,10 +149,10 @@ 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 — the SSE stream's last message is not
# delivered, so an App never leaves "loading". That is NOT reproduced in
# real Safari, 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 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
# resolved. An engine is either green or absent; a `continue-on-error`
# job would report coverage nobody is holding to a standard.
browser: [firefox]