Optimize for Task, ValueTask cases #81
hekuAnnotations
12 warnings
|
build-test-and-push
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-dotnet@v3, actions/upload-artifact@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L58
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L47
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithWaitAndReturn.cs#L42
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithWaitAndReturn.cs#L42
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberTaskAsyncWithReturn.cs#L27
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L58
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/Infrastructure/ClockTaskFactoryTests.cs#L47
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithWaitAndReturn.cs#L42
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)
|
|
build-test-and-push:
Kunet.AsyncInterceptor.Tests/TestsFromStakx/GetNumberValueTaskAsyncWithReturn.cs#L27
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)
|
|
Deprecation notice: v1, v2, and v3 of the artifact actions
The following artifacts were uploaded using a version of actions/upload-artifact that is scheduled for deprecation: "nuget".
Please update your workflow to use v4 of the artifact actions.
Learn more: https://github.blog/changelog/2024-04-16-deprecation-notice-v3-of-the-artifact-actions/
|
Artifacts
Produced during runtime
| Name | Size | |
|---|---|---|
|
nuget
Expired
|
9.77 KB |
|