Unexpected closed connection

Hey, team. I have found a strange behaviour in our application uses rust-libp2p.
For some reason we have a lot of errors with “Transport endpoint is not connected”. What can be a reason?

Below a trace log for yamux connection:

|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.781978Z TRACE                tokio ThreadId(07) yamux::connection::stream: ac9f498b/2: update state: (Open Closed Closed)    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.781934Z ERROR                tokio ThreadId(07) yamux::connection: ac9f498b: socket error: decode error: i/o error: i/o error: Transport endpoint is not connected (os error 107)    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.651741Z TRACE                tokio ThreadId(06) yamux::connection: ac9f498b/2: sending: (Header Data 2 (len 38) (flags 0))    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.651624Z TRACE                tokio ThreadId(06) yamux::connection::stream: ac9f498b/2: write 38 bytes    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.651052Z DEBUG                tokio ThreadId(03) yamux::connection: ac9f498b: new outbound (Stream ac9f498b/2) of (Connection ac9f498b Server (streams 0))    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.651033Z TRACE                tokio ThreadId(03) yamux::connection: ac9f498b/2: sending initial (Header WindowUpdate 2 (len 16515072) (flags 1))    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.651011Z TRACE                tokio ThreadId(03) yamux::connection: ac9f498b: creating new outbound stream    |
|2023-05-17T13:49:46+03:00|2023-05-17T10:49:46.650006Z DEBUG                tokio ThreadId(03) yamux::connection: new connection: ac9f498b (Server)    |

You might want to post this as an issue in the rust-libp2p repo