Test
Server Initiated Controller
Start the server first, then the client. The client advertises a listener, the server connects in, observes controller state, receives a control command, disconnects, and the matrix verifies the recorded command.
Total
14
pairings in this test
Passed
8
passing
Failed
6
failing
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
SendspinKit client conformance is intentionally disabled until the adapter can use the public SDK like an example application, without bespoke protocol code.
Server
aiosendspin
Client
aiosendspin
Controller command matched (next)
Server
aiosendspin
Client
sendspin-cpp
Controller command matched (next)
Server
aiosendspin
Client
sendspin-dotnet
Controller command matched (next)
Server
aiosendspin
Client
sendspin-go
Controller command matched (next)
Server
aiosendspin
Client
sendspin-js
sendspin-js client conformance is intentionally disabled until the adapter can use the public SDK like an example application, without bespoke protocol code.
Server
aiosendspin
Client
sendspin-rs
sendspin-rs-client build failed: [92m Compiling[0m crossbeam-queue v0.3.12
Server
sendspin-go
Client
SendspinKit
SendspinKit client conformance is intentionally disabled until the adapter can use the public SDK like an example application, without bespoke protocol code.
Server
sendspin-go
Client
aiosendspin
Controller command matched (next)
Server
sendspin-go
Client
sendspin-cpp
Controller command matched (next)
Server
sendspin-go
Client
sendspin-dotnet
Controller command matched (next)
Server
sendspin-go
Client
sendspin-go
Controller command matched (next)
Server
sendspin-go
Client
sendspin-js
sendspin-js client conformance is intentionally disabled until the adapter can use the public SDK like an example application, without bespoke protocol code.
Server
sendspin-go
Client
sendspin-rs
sendspin-rs-client build failed: [92m Compiling[0m crossbeam-queue v0.3.12