Uh oh!
There was an error while loading. Please reload this page.
chore(dispatcher): move potentiallyClosesScope into protocol metainfo - #40833
Conversation
Make `potentiallyClosesScope` a flag on protocol methods in protocol.yml, generate it into protocolMetainfo, and consult it solely from dispatcher.ts. Removes the field from CallMetadata and drops the per-dispatcher assignments. While there, `Frame.expect` no longer needs the flag: it already converts any thrown error (including TargetClosedError) into an ExpectResult.
Test results for "MCP"5 failed 7081 passed, 1104 skipped Merge workflow run. |
Test results for "tests 1"2 flaky41770 passed, 850 skipped Merge workflow run. |
8a21fee
into
microsoft:mainUh oh!
There was an error while loading. Please reload this page.
Summary
potentiallyClosesScopea flag on protocol methods inprotocol.yml, generated intoprotocolMetainfo, and consulted solely fromdispatcher.ts.CallMetadataand drop the per-dispatcherprogress.metadata.potentiallyClosesScope = trueassignments.Frame.expectno longer needs the flag: it already converts any thrown error (includingTargetClosedError) into anExpectResult.