Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-dotnet@v4, actions/upload-artifact@v4, darenm/Setup-VSTest@v1.3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Possible null reference argument for parameter 'value' in 'IReturnsResult<IServiceProvider> IReturns<IServiceProvider, object>.Returns(object value)'.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Null should not be used for type parameter 'vbucketId' of type 'short'. Use a non-null value, or convert the parameter to a nullable type. (https://xunit.net/xunit.analyzers/rules/xUnit1012)

Test methods should not use blocking task operations, as they can cause deadlocks. Use an async test method and await instead. (https://xunit.net/xunit.analyzers/rules/xUnit1031)

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Dereference of a possibly null reference.

Possible null reference argument for parameter 'value' in 'IReturnsResult<IServiceProvider> IReturns<IServiceProvider, object>.Returns(object value)'.

The annotation for nullable reference types should only be used in code within a '#nullable' annotations context.