versions used (SonarQube, Scanner, Plugin, and any relevant extension)
dotnet-sonarscanner : 4.8.0
SonarCloud : https://sonarcloud.io/dashboard?id=jhipster_jhipster-sample-app-dotnetcore
error observed (wrap logs/code around triple quote ``` for proper formatting)
java.lang.IllegalArgumentException: 60 is not a valid line offset for pointer. File src/JhipsterSampleApplication/Data/ApplicationDatabaseContext.cs has 50 character(s) at line 19
The analyse work locally with SonarQube
Github Actions :
Full log analyse in verbose mode :
12_RUN SONAR ANALYZE on generated app.txt (3.1 MB)
@nicolas63, it seems to be related to an open bug we have in the backlog https://github.com/SonarSource/sonar-dotnet/issues/2484
Is this fix for the msbuild version as well? I encounter this error with the msbuild version.
@danieldaeschle, can you please detail what error you are getting?
I was wrong there - it’s similar to the
#2484 issue, but not the same bug. We’d need more details from you to investigate.
please give us the verbose output of the
END step (please run
SonarScanner.MSBuild.exe begin /k:"MyProject" /d:sonar.verbose=true as the
BEGIN step, and please attach the output of
please give us the protobuf (
.pb) files which you find in the
.sonarqube\out\<NUMBER>\output-cs\ directories - the easiest is to do a ZIP archive of the
.sonarqube\out folder . Please note that the
.sonarqube folder gets generated during analyses and you can find it in the folder you run the commands from.
Hi, I have already share verbose log in my previous message. My error is only on my ci (GithubActions) so how to get .pb ?
Yes , you’re right.
so how to get .pb ?
On the build machine, in the folder where the SonarCloud scan is done, there’s a
.sonarqube folder inside which has various metadata for the scanner, including those protobuf files.
However, being an open-source project, we should be able to reproduce your problem ourselves. We’ll get back after we get some time to investigate.
Hi, sorry for the delay.
I have publish here .sonarqube :
@nicolas63 for following up. Before investigating on our side, could you take a look at this forum topic: 102 is not a valid line offset for pointer .
Do you have pre and post build events that modify the source code?
If you run
msbuild foo.sln /p:PreBuildEvent= /p:PostBuildEvent=
will it help ?
Hi, I have look the other topic and yes i have a ci step who add code, not in post build event but the principle is the same.
After correct this the sonar analysis work !!
Thanks for your help !
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.