Skip to content

Abandon workitem if processing workitem failed #682

Abandon workitem if processing workitem failed

Abandon workitem if processing workitem failed #682

Triggered via pull request September 16, 2025 19:01
Status Success
Total duration 9m 2s
Artifacts

codeQL.yml

on: pull_request
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

15 warnings and 1 notice
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp): test/TestHelpers/Logging/TestLogger.cs#L25
Nullability of reference types in return type of 'IDisposable? TestLogger<T>.BeginScope<TState>(TState state)' doesn't match implicitly implemented member 'IDisposable ILogger.BeginScope<TState>(TState state)' (possibly because of nullability attributes).
Analyze (csharp): test/TestHelpers/Logging/TestLogger.cs#L25
Nullability in constraints for type parameter 'TState' of method 'TestLogger<T>.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.
Analyze (csharp): test/TestHelpers/Logging/TestLogger.cs#L10
Nullability of reference types in return type of 'IDisposable? TestLogger.BeginScope<TState>(TState state)' doesn't match implicitly implemented member 'IDisposable ILogger.BeginScope<TState>(TState state)' (possibly because of nullability attributes).
Analyze (csharp): test/TestHelpers/Logging/TestLogger.cs#L10
Nullability in constraints for type parameter 'TState' of method 'TestLogger.BeginScope<TState>(TState)' doesn't match the constraints for type parameter 'TState' of interface method 'ILogger.BeginScope<TState>(TState)'. Consider using an explicit interface implementation instead.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
The target framework 'net6.0' is out of support and will not receive security updates in the future. Please refer to https://aka.ms/dotnet-core-support for more information about the support policy.
Analyze (csharp)
Unable to validate code scanning workflow: error: getWorkflow() failed: Error: Expected to find a code scanning workflow file at D:\a\durabletask-dotnet\durabletask-dotnet\.github\workflows\codeQL.yml, but no such file existed. This can happen if the currently running workflow checks out a branch that doesn't contain the corresponding workflow file.
Analyze (csharp)
The windows-latest label will migrate from Windows Server 2022 to Windows Server 2025 beginning September 2, 2025. For more information see https://github.com/actions/runner-images/issues/12677