Skip to content

Fix crash when two transports use colliding port ranges #777

Fix crash when two transports use colliding port ranges

Fix crash when two transports use colliding port ranges #777

Triggered via pull request November 21, 2024 12:30
Status Cancelled
Total duration 2m 6s
Artifacts

codeql.yaml

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

Annotations

6 errors and 6 warnings
Analyze (python)
Canceling since a higher priority waiting request for 'CodeQL-1469' exists
Analyze (python)
The operation was canceled.
Analyze (c-cpp)
Canceling since a higher priority waiting request for 'CodeQL-1469' exists
Analyze (c-cpp)
The operation was canceled.
Analyze (javascript-typescript)
Canceling since a higher priority waiting request for 'CodeQL-1469' exists
Analyze (javascript-typescript)
The operation was canceled.
Analyze (python)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
Analyze (python)
Unable to validate code scanning workflow: MissingPushHook
Analyze (c-cpp)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
Analyze (c-cpp)
Unable to validate code scanning workflow: MissingPushHook
Analyze (javascript-typescript)
1 issue was detected with this workflow: Please specify an on.push hook to analyze and see code scanning alerts from the default branch on the Security tab.
Analyze (javascript-typescript)
Unable to validate code scanning workflow: MissingPushHook