erezwanderman

Maybe the program should analyze the longest file name and directory name before starting and check if they are supported. So you won't get stuck with an error after many...

My way to handle such problems was to to set "Combine revisions within _ seconds, regardless of the comment." to 0. I suspect it might cause the process to take...

Yes, I used H.Formatters.MessagePack & H.Pipes.AccessControl in the original program but not in this reproduction example. Now added them in a new branch: https://github.com/erezwanderman/HPipeMultiClient/tree/MessagePack%26AccessControl. It does not change behaviour. still...

After analyzing it furthuer, I think that in IO/PipeStreamWriter.cs, PipeStreamWriter.WriteAsync, the call [BaseStream.WriteAsync](https://github.com/HavenDV/H.Pipes/blob/9299ffd93b5518a7c06e7fe12529bf45dfd8809c/src/libs/H.Pipes/IO/PipeStreamWriter.cs#L71) sends the response, and sometimes the client is fast enough to quickly disconnect before the server finishes...

Thanks! This fixes the issue and now the program works without exceptions.