failed to run Applicability scan
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Describe the bug
failed to run Applicability scan: [Thread 0] failed to run Applicability scan. Exit code received: exit status 51
Current behavior
18:33:12 [Debug] Executing /data/codeql/jfrog/temp/jfrog.cli.temp.-1760956333-778323183/dependencies/analyzerManager/analyzerManager zd /data/codeql/jfrog/temp/jfrog.cli.temp.-1760956343-165009068/Sast_1760956392/config.yaml /data/codeql/jfrog/temp/jfrog.cli.temp.-1760956343-165009068/Sast_1760956392/results.sarif 0da3f39c-ada0-11f0-b6b0-fa163e800e44
18:33:55 [🔵Info] [Thread 0] Found 7 SAST vulnerabilities
18:33:55 [Debug] Sending HTTP PUT request to: https://inner-global-prod-jfrog-8081.skx-internal.com/xray/api/v1/xsc/event
18:33:55 [Debug] Command event:
{{0 failed 0 0 false 1m37.033347942s } 0da3f39c-ada0-11f0-b6b0-fa163e800e44 }
18:33:56 [Debug] Sending an error report to JFrog analytics...
18:33:56 [Debug] Sending HTTP POST request to: https://inner-global-prod-jfrog-8081.skx-internal.com/xray/api/v1/xsc/event/logMessage
18:33:56 [🚨Error] target '/home/java_app/upex-get-data [maven]' errors:
failed to run Applicability scan: [Thread 0] failed to run Applicability scan. Exit code received: exit status 51
Reproduction steps
frogbot scan-repository
Expected behavior
No response
JFrog Frogbot version
2.27.2
Package manager info
pom.xml
Git provider
GitHub
JFrog Frogbot configuration yaml file
No response
Operating system type and version
Linux jfrog 5.10.0-136.12.0.86.r1526_92.hce2.x86_64 #1 SMP Tue Mar 26 03:00:47 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
JFrog Xray version
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the frogbot scan-repository reproduction and the pom.xml target, then inspect the logged analyzerManager command and exit status 51. Compare behavior on Frogbot 2.27.2 under the reported Linux environment; done means the Applicability scan completes without the reported failure, with the underlying cause documented or fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, linux
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100