Vs code extensions improvements #40
Merged
Annotations
11 warnings
|
Complete job
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3, actions/setup-dotnet@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L163
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L155
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L130
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L127
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L144
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L92
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L81
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L69
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/EventExportImportServiceTests.cs#L58
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
|
Build:
tests/LightQueryProfiler.Shared.UnitTests/Services/DatabaseEngineDetectorTests.cs#L21
Calls to methods which accept CancellationToken should use TestContext.Current.CancellationToken to allow test cancellation to be more responsive. (https://xunit.net/xunit.analyzers/rules/xUnit1051)
|
Loading