Process completed with exit code 9.

We were unable to automatically build your code. Please replace the call to the autobuild action with your custom build steps. Encountered a fatal error while running "/opt/hostedtoolcache/CodeQL/2.19.4/x64/codeql/java/tools/autobuild.sh". Exit code was 1 and last log line was: Picked up JAVA_TOOL_OPTIONS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false. See the logs for more details.

Unexpected input(s) 'run', 'shell', valid inputs are ['name', 'path', 'if-no-files-found', 'retention-days', 'compression-level', 'overwrite', 'include-hidden-files']

No files were found with the provided path: results/java.sarif. No artifacts will be uploaded.

Unexpected input(s) 'mobb-project-name', valid inputs are ['report-file', 'api-key', 'github-token', 'scanner']

Unexpected input(s) 'mobb-project-name', valid inputs are ['report-file', 'api-key', 'github-token', 'scanner']

CodeQL Action v2 will be deprecated on December 5th, 2024. Please update all occurrences of the CodeQL Action in your workflow files to v3. For more information, see https://github.blog/changelog/2024-01-12-code-scanning-deprecation-of-codeql-action-v2/

This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration

Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.19.4.

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.