Occasionally we'd see chunkLength errors from StringWriter.ToString() calls after connecting. I think we've isolated this (via test stress runs) down to a write happening post-lock on the TextWriterLogger disposal. This lock in dispose ensures we're not trying to write to a writer we should have fully released at the end of a .Connect()/.ConnectAsync() call.
Occasionally we'd see
chunkLengtherrors fromStringWriter.ToString()calls after connecting. I think we've isolated this (via test stress runs) down to a write happening post-lock on theTextWriterLoggerdisposal. This lock in dispose ensures we're not trying to write to a writer we should have fully released at the end of a.Connect()/.ConnectAsync()call.