Case

sendspin-server-cpp -> sendspin-rs

Start the server first, then the client. The client discovers or looks up the server and initiates the WebSocket connection, the server sends a metadata state update, disconnects, and the matrix compares a normalized metadata snapshot and checks that the first state carrying a metadata object bore a past or present timestamp.

Server

sendspin-server-cpp

Client

sendspin-rs

Status

Failed

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-metadata

Inspection

Summaries, logs, and builds

Matrix result

RAW
{
  "case_dir": "artifacts/results/data/macos__client-initiated-metadata__sendspin-server-cpp__to__sendspin-rs",
  "client_exit_code": 1,
  "client_impl": "sendspin-rs",
  "reason": "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-metadata",
  "scenario_id": "client-initiated-metadata",
  "scenario_revision": 1,
  "server_exit_code": 1,
  "server_impl": "sendspin-server-cpp",
  "status": "failed",
  "unsupported": false
}