I received your logs and it does indeed seem like the analysis hangs for more than half an hour on a single file. This is unexpected.
Out of curiosity, does your project use promise chains? @ms1111 was kind enough to share a small reproducer of their problem with me. We idenfitied the issue: It was due to a bug when analyzing promise chains. We fixed this and it should be released to SonarQube Cloud very soon (within the next 24 hours). If your problem is indeed the same, then it should be fixed.
Michael, Tatah, I will let you both know when this is available on SonarQube Cloud and I would appreciate your feedback whether it fixes your problems.
@ms1111 We are now live with a new version of the sensor that fixes the issue that you reported and provided a reproducer for. Thank you again! Can you try again (with the new sensor & the problematic file not excluded) and let me know if your problem is fixed?
@tatah If your problem was indeed the same, it should be fixed as well. Can you also try and give us feedback?
Hey Malte, sorry to barge in, but we recently started having the same issue of sonarjasmin just hanging and never finishing (it actually started taking hours and hours to finish, when it did)
The average time for the analysis went from 7 minutes to up to 4 hours starting on June 17th. After some debugging, we found that it suddenly started hanging on sonarjasmin on the server index.js file for the server (nodejs + express). Ok, we excluded that and it started “working” again, but averaging 17 minutes, worse, but manageable.
Up until 4 days ago, June 26th, that it started hanging but even worse now (now it was taking 6+ hours and never finishing). I’ve started debugging again and it looks like the route files for our project are either hanging indefinitely or taking too long to be analyzed.
I am posting on this topic due to the timings of the issues: seems like the latest fix actually broke something on our side. I’ve tried excluding the first route file that was just hanging forever, only to find out that it would hang later in another one.
Hey @mauriciocavalcanti, thank you very much for the feedback and welcome to the community!
We are committed to making the new engine work smoothly for everyone, so I’d love to dig a bit deeper with you. To start with, could you provide me with some debug logs? You can get debug logs by adding the flag -Dsonar.verbose=true to the scanner.
I will also initiate a private thread with you in case you are not comfortable sharing the debug logs publicly.
