The client example provided by the C API is inconsistent with multiple execution results?

[muyiwq]

Regardless of the previous version or the latest version, the execution result of the client.c executable program provided by the c API is different each time. There are three situations in which the client connects to the server multiple times to execute the result. One is to send streaming data normally and close the connection. One is to establish a connection, unable to send stream data, and unable to close the connection. The last one is to establish a connection and send streaming data, but the connection cannot be closed normally. Is this normal? I checked the problem and I guessed that the time returned by quiche_conn_timeout_as_nanos() was incorrect. When the client was closed abnormally, the program debugging went to the is_draining branch of the function timeout() in lib.rs. When the program should not be draining the connection, the program is sometimes closed. How to solve it? What should I do to allow the client to send stream data normally every time and close the connection normally? Can you give me some suggestions, looking forward to your reply?

[LPardue]

Hey. We'd more debug logs and more specific reproduction steps to really understand what the issue is.

[LPardue]

Closing due to inactivity.