Request-Response Protocol Unexpected Eof

[anilaltuner]

Description

I'm encountering an UnexpectedEof error when sending a small request payload to a peer. The error occurs during the request-response protocol communication.

The request data (in decimal byte array):
[123, 34, 114, 101, 113, 117, 101, 115, 116, 95, 105, 100, 34, 58, 34, 99, 48, 98, 57, 101, 48, 51, 51, 45, 98, 56, 99, 57, 45, 52, 56, 100, 97, 45, 98, 102, 100, 50, 45, 100, 56, 100, 98, 101, 55, 50, 48, 99, 102, 51, 100, 34, 125]

When decoded, this represents a JSON payload:
{"request_id":"c0b9e033-b8c9-48da-bfd2-d8dbe720cf3d"}

Error Logs

[2025-01-15T08:35:20Z ERROR dkn_rpc::p2p::client] Sent request to peer <peer_id>
[2025-01-15T08:35:22Z ERROR dkn_rpc::p2p::client] Request-Response: Outbound failure to peer <peer_id> with request_id 1: Io(Custom { kind: UnexpectedEof, error: Eof { name: "array", expect: Small(1) } })

The request was successfully sent to the peer
The connection was terminated unexpectedly while reading the response
The system was expecting to read at least one more byte (Small(1)) from an array when the connection ended

The code I used;

                       
 let data = serde_json::to_vec(&serde_json::json!({
                            "request_id": format!("{}", Uuid::new_v4()),
                        })).unwrap();
                        
self.swarm
     .behaviour_mut()
     .request_response
     .send_request(&peer_id, data);

I send request just after I discovered identity on Kademlia.

Also, I am using cbor and my request type is Vec<u8>

What can be problem in here?

[elenaf9]

Hi @anilaltuner, what transport are you using?

[anilaltuner]

Hey @elenaf9, I'm using tcp and quic

        let mut swarm = SwarmBuilder::with_existing_identity(local_key.clone())
            .with_tokio()
            .with_tcp(
                tcp::Config::default(),
                noise::Config::new,
                yamux::Config::default,
            )?
            .with_quic()
            ...

[anilaltuner]

I think I have a problem on protocol string. When I make sure requester and responder has same protocol string, it resolves.