Pipeline hangs in Sonar after displaying the JsSecuritySensorV2 task. This Sonar scan ran without issues a month ago. I’m using the same repository without modifications, with Azure agents. I’ve adjusted memory and other settings, but it keeps hanging. Why did it start hanging if it didn’t happen before? I’m sending the latest log.
SonarLog.txt (1.2 MB)
Hi,
Welcome to the community and thanks for this report!
Thanks also for starting with a debug log! 
Can you characterize app.js? Would it be possible to share it?
Thx,
Ann
Sure, attach the app.js
app.zip (2.8 KB)
Hi,
Thanks for the file!
I’ve flagged this for the language experts.
Ann
Hi @bicolorman, thank you for reporting this!
I tried reproducing the issue using only app.js, but the analysis terminates quickly. This is expected since most of the imports cannot resolve, leaving little for the tool to analyze.
Would it be possible to share more of the codebase so we can properly reproduce, investigate, and fix the issue? You can post it here, or let me know if you’d prefer to share it privately and I can send you a direct message.
A minimal reproducible example would be ideal. However, if creating one is too time-consuming and you don’t mind sharing the full source code, a non-minimal version would still be incredibly helpful.
Thanks!
Samuele
Hi, Yes I want to share privately.
The fix was just merged! We will release a new version of the analyzer next week, and it will be deployed to SQC shortly after.
Thanks again, @bicolorman, for reporting this issue and helping us uncover a tricky bug in the engine.