You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 37a5ad4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(ios): disclose whether a canceled read-only runner send was written (#3409)
* fix(ios): disclose whether a canceled read-only runner send was written
Follow-up to #3385. The read-only route (waitForRunner) threw a bare
canceled error, so a cancellation that landed before any connect attempt
was charged and drained with one status poll instead of withdrawn. It now
discloses `dispatched: no` when no attempt could have written the
command, and `unknown` once an attempt was interrupted mid-flight or an
earlier attempt may have written it.
Pins two exchange behaviors with tests: a refused connection withdraws
its charge whether or not the request was canceled (the runner never
received the command), and a drain whose status read fails stops at once
with the charge left abandoned.
Refs #3383
Co-Authored-By: Claude Opus 5.5 <[email protected]>
* fix(ios): keep dispatched no when a canceled runner route proves nothing was written
Each route of the read-only connect loop replaced its failure with a bare
canceled error, so a cancellation whose own failure proved nothing was
written (a usbmux connect still in progress, a refused fetch, a simulator
curl that could not connect) reported `dispatched: unknown`. Routes now
keep `no` when that failure is the proof, and the final simulator post
combines the loop's write evidence with its own failure the same way.
An abort that interrupts a POST, or the request's shared abort reason,
still reads as possibly written.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
---------
Co-authored-by: Claude Opus 5.5 <[email protected]>
0 commit comments