@flux-control/effect-modbus-rs
    Preparing search index...

    Interface TransportResilienceOptions

    Resilience configuration accepted by every transport service alongside its modbus-rs options.

    Both are opt-in: with neither set, a transport behaves exactly as it always has — one attempt per operation, reconnection only when asked for.

    interface TransportResilienceOptions {
        connectTimeout?: Input;
        reconnect?: ReconnectOptions;
        retry?: ModbusRetryPolicy;
    }
    Index
    connectTimeout?: Input

    Time limit for each operation that waits for an open or reconnect of the underlying transport.

    The modbus-rs bindings do not limit the connect time. A TCP connect to a host that does not answer waits until the operating system stops it, which takes about 2 minutes on Linux with default settings.

    The limit applies independently to each caller that waits for an open or reconnect. When it expires, that caller fails with ModbusTimeoutError.

    The native connect cannot be cancelled, so it continues. Later callers wait for the same native connect, each for at most this limit, so one transport has at most one pending native connect. When the native connect succeeds later, the transport uses it. When it fails, the next caller starts a new connect. Unbounded by default.

    reconnect?: ReconnectOptions

    Hands reconnection to a supervisor fiber owned by this transport, and enables the circuit breaker that keeps callers off a dead bus.

    Retry policy applied to every operation of every client from this transport. Overridable per client and per operation.