Hi all,
It’s August, which means half of our European offices are currently ghost towns as everyone enjoys their summer holidays. But don’t worry - we’re still here, keeping the lights on!
While our colleagues are off enjoying beaches, mountains, and new cities, the community keeps on contributing important feedback.
As always, we want to take a moment to recognize everyone who sparked interesting discussions and gave us valuable feedback to drive continuous improvement.
SonarQube Server & SonarQube Community Build:
- @gquerret reported that after upgrading to 2025.4.1, all projects show empty main branches on the overview page, though the data is still accessible when clicking into individual projects. Turns out we had a pretty serious bug in this release that affected Developer Edition only. We’ve already fixed it with 2025.4.2! Thanks to @gquerret for the report (and providing a database backup privately where we could easily reproduce the issue), and @niraj_125, @PaulAnand, @JCradock, @progs, @Orazio_Italiano, @Luca.i and @aozmez for the additional reports!
SonarQube Cloud:
- We had a very frustrating incident on SonarQube Cloud this week where the scanner would fail to upload the analysis report with a java.net.SocketTimeoutException: timeout error. There are too many people to thank for reporting this, so I’ll just name @SvenC and @daogilvie for making the first two reports that kicked off the investigation. After trying many things, it turned out to be a bug introduced by our cloud provider. The rollout of the fix should be almost complete now.
Thanks everyone for your patience while we worked on resolving this issue. - @daniel.schiffl noticed that merge information (like my-feature → master) disappeared from the SonarQube Cloud UI. This was an unintended consequence of a recent update and we’ve already fixed the issue. Thanks a lot for the report!
SonarQube for IDE:
- @reimorster discovered that IntelliJ’s pre-commit analysis gets stuck indefinitely when SonarQube for IDE tries to analyze files that aren’t actually analyzable (like .idea config files). Since the analysis never starts when no valid files are found, no completion response is sent back, leaving the UI frozen. The team created SLCORE-1583 to solve this. Thanks!
Rule & Language Improvements:
- @ftlvz is working with Microsoft Fabric’s unique approach where Jupyter Notebooks are saved as .py files instead of .ipynb. This causes parsing errors with notebook-specific commands like %run. We created a ticket to investigate detecting notebook usage regardless of file extension!
Thank you again to everyone mentioned—and to those we may have missed—for your ongoing contributions in making this community stronger and helping us improve Sonar products.
If you’d like to give a shout-out to someone, whether a community member or a SonarSourcer who helped you, please do so below. And if there’s someone you think we should acknowledge next week, let us know!