-
Notifications
You must be signed in to change notification settings - Fork 276
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metric 'files' should not be computed by a sensor #212
Comments
same problem there
hope for a sooner update |
Same issue here INFO: SonarQube Scanner 3.2.0.1227 |
Same issue, Hope having update soon |
Same Issue, hope to have an update soon.. INFO: SonarQube Scanner 3.3.0.1492 |
Same Issue here INFO: SonarQube Scanner 3.3.0.1492 |
Same Issue INFO: SonarQube Scanner 3.3.0.1492 |
I have the same issue INFO: SonarQube Scanner 3.3.0.1492 Workaround: |
Same Issue here INFO: SonarQube Scanner 3.3.0.1492 |
Same Issue here INFO: SonarQube Scanner 3.3.0.1492 |
we have soled the problem according to the Workaround replyed by jpiechowka |
Here's how to work around this issues, together with many other tips onmyway133/blog#216 |
Did the changes proposed by onmyway133 but get the same error... |
Facing Same issue. |
Absolutely same here.
|
I have followed the suggestion from @jpiechowka and recompiled the source code of the plugin with the lines commented out. Now I get a new error :/
|
The patch worked for me. Note that you have to remove FILES and LINES metrics for both Swift and Objective-C. So four lines need to be removed. |
* 0.4.4-volvo: Fixed "ERROR: Metric 'files' should not be computed by a Sensor". Issue: Idean#212. PR: Idean#213 # Conflicts: # commons/pom.xml # objclang/pom.xml # objclang/src/main/java/com/backelite/sonarqube/objectivec/ObjectiveCSquidSensor.java # pom.xml # sonar-swift-plugin/pom.xml # swiftlang/pom.xml # swiftlang/src/main/java/com/backelite/sonarqube/swift/SwiftSquidSensor.java
@ivelius Removing those entries with number="0" in my cobertura report xml file allowed me to upload to sonar, but i dont know why they're being generated in the first place :/ |
Same Issue here INFO: sonar-scanner-4.0.0.1744-macosx |
Same isse here |
Facing same issue |
I could fix this issue with the workaround suggested here: https://dev.to/onmyway133/how-to-use-sonarqube-in-swift-projects-5db5 However, I get a different issue now:
Does anyone know what this is about? |
what would be the correct way that maintainers would solve this?? so that it can be merged into master/dev and get a new official release that support current sonar? |
Tracked to a change in 7.7 https://docs.sonarqube.org/latest/setup/upgrade-notes/#header-4 And apparently this commit SonarSource/sonarqube@f6b2a26#diff-958438b627eede67724e05feb7d35e69 SonarOpenCommunity/sonar-cxx#1696 solved in a comment there to SonarOpenCommunity/sonar-cxx#1729 this merge solved it SonarOpenCommunity/sonar-cxx#1695 |
#238 should fix this issue. Awaiting merge. |
Nice, we will have a new release (specifiying incompatibility.. or we will just compile the version?) |
We have to discuss if we should embed this fix or not, regarding the incompatibility. |
Can any one help with working sonar plugin by fixing below issue |
New release embed this fix. Closing this issue. |
Getting same Metric files error...can i use this plugin in Linux? OS:linux |
Describe the bug
When running run-sonar-swift.sh, I get an error during the sonar-runner phase.
If I run the sonar-runner alone (with -X option), I get the following java call stack.
I guess the plugin is not compatible with SonarQube 7.7, but maybe it is only the
saveMeasures
of SwiftSquidSensor to update ?Screenshots
SonarQube environment:
The text was updated successfully, but these errors were encountered: