chore: add extra cache step #799
Annotations
13 warnings
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
|
|
|
|
|
|
|
|
test/unit/LocalGroupProcessorTest.cs#L77
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
test/unit/LocalGroupProcessorTest.cs#L94
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
test/unit/GPOLocalGroupProcessorTest.cs#L209
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
test/unit/GPOLocalGroupProcessorTest.cs#L221
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
test/unit/GPOLocalGroupProcessorTest.cs#L238
This async method lacks 'await' operators and will run synchronously. Consider using the 'await' operator to await non-blocking API calls, or 'await Task.Run(...)' to do CPU-bound work on a background thread.
|
|
test/unit/ACLProcessorTest.cs#L695
The variable 'expectedRightName' is assigned but its value is never used
|
|
test/unit/ACLProcessorTest.cs#L802
The variable 'expectedRightName' is assigned but its value is never used
|
|
test/unit/ACLProcessorTest.cs#L876
The variable 'expectedRightName' is assigned but its value is never used
|
This job succeeded
Loading