Emmanuel André

I have just discovered that @StephenCleary has already written such a class that he called [`AsyncStreamBase`](https://github.com/StephenCleary/ProducerConsumerStream/blob/master/ProducerConsumerStream/Internal/AsyncStreamBase.cs) inside the [ProducerConsumerStream](https://github.com/StephenCleary/ProducerConsumerStream) repository. It is quite the same approach, except that the protected...

Thanks, now I understand the intent of the `bool sync` pattern. I have updated the [`AsyncStream`](https://github.com/manandre/FollowingFileStream/blob/async-ex-flag/FollowingFileStream/AsyncStream.cs) class inside my project accordingly. I propose to add it as an helper class...

@roji and @vonzshik, your comments are welcome.

@roji I have just rebased. However, I am still not fully confident around the lock replacement in the `Close` method of the `NpgsqlConnector` class... IMHO No hurry is required here,...

I also reproduced the issue with Npgsql but not with SqlServer from the same setup. Code setup ```cs using Microsoft.EntityFrameworkCore; using Npgsql; using OpenTelemetry; using OpenTelemetry.Resources; using OpenTelemetry.Trace; using System.Diagnostics;...

I have found a possible explanation inside build logs: ``` [INF] "/home/runner/work/csharp-language-server-protocol/csharp-language-server-protocol/test/coverlet.runsettings" is not a valid Coverage settings file. Using default values. ``` But I do not see which part...

Solution found! The DataCollector must be named `code coverage` and not `XPlat code coverage`.

Surprising. The previous step is also using a relative path `artifacts/logs/` and seems to work correctly.

The CI checks seem blocked in an infinite wait, even after a new commit on the PR branch... Can someone help me to solve this ?

> > The CI checks seem blocked in an infinite wait, even after a new commit on the PR branch... Can someone help me to solve this ? > >...