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 a880362
Browse filesBrowse the repository at this point in the historyBrowse files
fix: typed cancellation everywhere + own the AWS remote-access ARN through startup
Second-order follow-ups the #1774 refactor made cheap:
- markRequestCanceled aborts the request signal WITH the kernel's typed
canceled error as its reason. Every signal.throwIfAborted(), aborted fetch,
and 'throw signal.reason' in the daemon (20+ sites) now surfaces a canceled
request as such instead of a bare DOMException that normalized to UNKNOWN —
and no site has to know the factory exists.
- AWS Device Farm prepareSession owns the remote-access ARN from the moment
create-remote-access-session answers: a startup timeout, the allocation
deadline, or a canceled request now stops it before the failure surfaces
(previously a timed-out startup left a RUNNING billed session behind — the
same leak class as the WebDriver session, one phase earlier). The startup
wait is capped by LeaseLifecycleContext.deadline and wakes on cancellation.
- BrowserStack's pre-session local app upload honors the request signal (an
upload is not billed, so plain abort is right there).
- lease_heartbeat/lease_release share lease_allocate's preserve-daemon policy:
the rationale — the daemon owns billed sessions; a reset orphans them all —
applies verbatim.
Each AWS ownership test proven red without the guard (3/3).
0 commit comments