Skip to content

Merge pull request #9 from gemstone/development #182

Merge pull request #9 from gemstone/development

Merge pull request #9 from gemstone/development #182

Triggered via push January 7, 2026 19:08
Status Success
Total duration 1m 40s
Artifacts
Matrix: Analyze
Fit to window
Zoom out
Zoom in

Annotations

11 warnings
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L726
Possible null reference return.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L707
Possible null reference return.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L683
Possible null reference return.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L656
Cannot convert null literal to non-nullable reference type.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L635
Possible null reference assignment.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L545
Non-nullable field 'm_processTimer' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L545
Non-nullable field 'm_name' must contain a non-null value when exiting constructor. Consider adding the 'required' modifier or declaring the field as nullable.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L572
Nullability of reference types in type of parameter 'sender' of 'void ProcessQueue<T>.ProcessTimerThreadProc(object sender, ElapsedEventArgs e)' doesn't match the target delegate 'ElapsedEventHandler' (possibly because of nullability attributes).
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L528
Cannot convert null literal to non-nullable reference type.
Analyze (csharp): src/Gemstone.Threading/Collections/ProcessQueue.cs#L499
Cannot convert null literal to non-nullable reference type.
Analyze (csharp)
CodeQL Action v3 will be deprecated in December 2026. Please update all occurrences of the CodeQL Action in your workflow files to v4. For more information, see https://github.blog/changelog/2025-10-28-upcoming-deprecation-of-codeql-action-v3/