Test
Client initiates connection and client wants Controller
Start the server first, then the client. The client discovers or looks up the server and initiates the WebSocket connection, the server observes controller state, receives a control command, disconnects, and the matrix verifies the recorded command.
Total pairings
12
Passed
7
Failed
5
Runs
Server and client pairings
Open a case to inspect the full hello payloads, summaries, logs, and build output for that pairing.
Server
aiosendspin
Client
SendspinKit
Controller command matched (next)
Server
aiosendspin
Client
aiosendspin
Controller command matched (next)
Server
aiosendspin
Client
sendspin-cpp
Controller command matched (next)
Server
aiosendspin
Client
sendspin-dotnet
Client controller state reports no supported_commands list
Server
aiosendspin
Client
sendspin-js
Controller command matched (next)
Server
aiosendspin
Client
sendspin-rs
Server adapter reported: Timed out waiting for client 'sendspin-rs-client'; Client adapter reported: Harness gap, not a protocol result: the sendspin-rs client adapter has no client-initiated path for scenario client-initiated-controller; Timed out after 40s waiting for the server adapter to exit
Server
sendspin-server-cpp
Client
SendspinKit
Controller command matched (next)
Server
sendspin-server-cpp
Client
aiosendspin
Controller command matched (next)
Server
sendspin-server-cpp
Client
sendspin-cpp
Controller command matched (next)
Server
sendspin-server-cpp
Client
sendspin-dotnet
Client controller state reports no supported_commands list
Server
sendspin-server-cpp
Client
sendspin-js
Server adapter reported: the client sent client/hello but never took the connection with a client/state after server/activate; handshake failed
Server
sendspin-server-cpp
Client
sendspin-rs
Server adapter reported: no client completed the handshake with a client/hello; Client adapter reported: Harness gap, not a protocol result: the sendspin-rs client adapter has no client-initiated path for scenario client-initiated-controller