Scanner command used when applicable: using autoscan
Languages of the repository: PHP (CakePHP specifically)
Error observed: No errors that I can find but that the last analysis failed with code: AW4EIpwnje0MfGYyGHBP
I have linked a github repo to my sonarcloud account. It finds it, the sonarcloud app is installed on github. I added the .sonarcloud.properties files with a few folders excluded (first attempt was with an empty properties file). It keeps failing with the same message that the analysis failed (no details)
My properties file looks like this (I assume multiple folders should be separated by commas⌠the documentation doesnât specify):
Hello,
On Backgroud Tasks there is a button, which allows you to see the logs:
Without error logs (`Show Error Details) nobody is able to help you.
Second thing, I believe that people are ignoring your help request, because you posted analysis ID (three times) as error codes. There are many help requests, many are the same, so when community users see that:
product name is spelled incorrectly
basic information are missing, example:
version of: SonarQube, plugins, SonarScanner
full project configuration
lack of understanding of the product (example: error code = analysis id)
Thanks @agabrys for chiming in. Unfortunately it seems you overlooked an important element in the userâs post: he did check the Background Tasks page and found nothing there. Please read more carefully next time, and I personally found your tone unfriendly.
Second thing, we (SonarSource team) were not ignoring the request, weâre just overloaded. The âlast analysis failedâ type of help requests are following a direct advice from SonarCloud itself, when it happens. So, for one thing, we certainly wonât ignore these, and for another thing, we should really improve the product to make these cases rare events.
@BenOberholzer Our investigation is in progress. For now, I can just tell you that some files appear to have invalid UTF-8 characters. I will share with you the list in a private message. But why do we care about UTF-8 you might ask. We try to detect the right encoding, and for these files we couldnât, and in such cases we fall back on UTF-8 as default. If thatâs not the correct encoding for your project, then you can set sonar.sourceEncoding=... in your .sonarcloud.properties file to the correct one.
Hello @janos, I didnât want to be rude/unfriendly. If my answer sounded like that, I apologize. I just wanted to point that if somebody from support/community has some free time and dozen of requests, then he/she will pick up this one which a lot of details. Why? Because it has a higher chance to be solved
I didnât miss it I read:
For my understanding it doesnât mean that there is no error. Maybe there is an error, but the error message doesnât point directly to the problem. I donât know, I donât see it
If SonarSource team read all help requests, then it is really cool