CodeQL Analysis #947
codeql-analysis.yml
on: schedule
CodeQL Analysis
1m 41s
Annotations
9 warnings
CodeQL Analysis
ubuntu-latest pipelines will use ubuntu-24.04 soon. For more details, see https://github.com/actions/runner-images/issues/10636
|
CodeQL Analysis:
src/kibali/AuthZChecker.cs#L46
'Uri.Uri(Uri, string?, bool)' is obsolete: 'This constructor has been deprecated; the dontEscape parameter is always false. Use Uri(Uri, string) instead.'
|
CodeQL Analysis:
src/kibali/AuthZChecker.cs#L46
'Uri.Uri(Uri, string?, bool)' is obsolete: 'This constructor has been deprecated; the dontEscape parameter is always false. Use Uri(Uri, string) instead.'
|
CodeQL Analysis:
src/kibaliTool/ExportCommand.cs#L10
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.
|
CodeQL Analysis:
src/kibaliTool/ValidateCommand.cs#L20
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.
|
CodeQL Analysis:
src/kibaliTool/DocumentCommand.cs#L19
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.
|
CodeQL Analysis:
src/kibaliTool/ExportCommand.cs#L10
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.
|
CodeQL Analysis:
src/kibaliTool/ValidateCommand.cs#L20
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.
|
CodeQL Analysis:
src/kibaliTool/DocumentCommand.cs#L19
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.
|