Hey Martin,
I know you can workaround the problem by excluding a specific file as discussed via private message. Here’s a quick status update on the new sensor.
After some investigation following a small reproducer from another user who ran into the same problem here, we identified a bug in the new sensor involving the analysis of promise chains. Does your project use such promise chains? If yes, it is not unlikely that the analysis took longer due to this.
We also implemented another general performance improvement that helps to boost performance in certain situations.
Both of these will be released to SonarQube Cloud within the next 24 hours. I will let you know when this is available and I would appreciate your feedback whether you are seeing a performance improvement. ![]()