cdp-command-timeout-error
The distinct error the desktop CDP transport raises when a single CDP command gets no response within commandTimeoutInMilliseconds.
It exists as a type rather than a bare Error so ONE caller can tell it apart: evaluate(), which is the only Runtime.evaluate carrying a test’s own closure, re-reports it as EvalCapExceededError. The harness’s other Runtime.evaluate calls — the trust dialog, the parent-liveness watchdog, the boot probes — time out for reasons that have nothing to do with a test waiting too long, and matching them on the method name would produce exactly the misdiagnosis this work removes, pointing the other way.
Classes
Section titled “Classes”| Class | Description |
|---|---|
| CdpCommandTimeoutError | Thrown when a CDP command gets no response within the transport’s per-command timeout. Carries the method and the budget so a caller can instanceof-match and re-report it in its own terms. |
Interfaces
Section titled “Interfaces”| Interface | Description |
|---|---|
| CdpCommandTimeoutErrorConstructorParams | Parameters for the CdpCommandTimeoutError constructor. |