Krikri::SSHManager::DaemonDispatchUnknownError
Raised when a daemon request WAS sent (the frame was fully written into the pipe) but no usable response came back - a timeout waiting for the response, a truncated/malformed frame, an unparseable one. In that state the module may already have run inside the daemon, so the caller must NOT re-execute it over a fallback transport: a non-idempotent module (a bare command:, an append, an email) would apply twice. See PluginManager#execute_remote_plugin_transport, which turns this into a failed-task result instead of its usual fall-through to the one-shot path - or, when #transport_lost? is set (the pipe itself died or timed out on a cached daemon), into an UNREACHABLE result, which is how Ansible classifies a connection that dies while its module runs.
Constructors
Instance methods
True when the response was lost because the pipe/transport itself died or timed out on an already-cached daemon (EOF on the read, a hung read hitting the wall-clock timeout). Real Ansible books a connection that dies while its module runs as UNREACHABLE - the host is dropped from the play and the run exits 4 - not as a failed (ignorable) task. False for a daemon that answered with unusable bytes (framing garbage): there the transport is alive, the module ran and produced garbage, which stays a failed task.