Change return type of method 'WaitAsync' from 'System.Threading.Tasks.Task' to 'System.Threading.Tasks.Task<bool>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)

ValueTask instances returned from method calls should always be used, typically awaited. Not doing so often represents a functional bug, but even if it doesn't, it can result in degraded performance if the target method pools objects for use with ValueTasks. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2012)

Change return type of method 'WaitAsync' from 'System.Threading.Tasks.Task' to 'System.Threading.Tasks.Task<bool>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)

ValueTask instances returned from method calls should always be used, typically awaited. Not doing so often represents a functional bug, but even if it doesn't, it can result in degraded performance if the target method pools objects for use with ValueTasks. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2012)

Change return type of method 'WaitAsync' from 'System.Threading.Tasks.Task' to 'System.Threading.Tasks.Task<bool>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)

ValueTask instances returned from method calls should always be used, typically awaited. Not doing so often represents a functional bug, but even if it doesn't, it can result in degraded performance if the target method pools objects for use with ValueTasks. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2012)

Change return type of method 'WaitAsync' from 'System.Threading.Tasks.Task' to 'System.Threading.Tasks.Task<bool>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)

ValueTask instances returned from method calls should always be used, typically awaited. Not doing so often represents a functional bug, but even if it doesn't, it can result in degraded performance if the target method pools objects for use with ValueTasks. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2012)

Change return type of method 'WaitAsync' from 'System.Threading.Tasks.Task' to 'System.Threading.Tasks.Task<bool>' for improved performance (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca1859)

ValueTask instances returned from method calls should always be used, typically awaited. Not doing so often represents a functional bug, but even if it doesn't, it can result in degraded performance if the target method pools objects for use with ValueTasks. (https://learn.microsoft.com/dotnet/fundamentals/code-analysis/quality-rules/ca2012)

Cannot build an overlay database because build-mode is set to "undefined" instead of "none". Falling back to creating a normal full database instead.