Exception in thread "main" java.lang.NumberFormatException: For input string: "AboveAverage.cs" about sonar-cnes-report

[begarco]

Hi @difeijin,

Please rewrite your issue like in the template we provide.

It seems to be a specific C# plugin related issue(C# metric) , but we need more information about your use case to reproduce it and fix it.

Regards,
Benoît

[begarco]

Please use edit feature of GitHub issues instead of duplicating them.

[begarco]

@difeijin I gather all your information in that issue.

Could you provide us your list of installed plugins and their versions?

[astrasia]

I have a similar issue. I don't think it is related to C# as I am using PHP (my guess). The errors line are exact.

I have very limited plug-ins installed, all are the default from SonarQube installation. CNES is the only plug-in I added.

[begarco]

Hello @astrasia,

Could you send us the content of 404.php, or a piece of project with which we can reproduce thius error?

Thanks.

[Sancretor]

Hi @astrasia,

Just a quick reminder.
In order to investigate, we really need an example file that triggers this error.
Thanks !

[difeijin]

AboveAverage.cs is the first file in name order in my project which has a lot of csharp files.I have try put this file(AboveAverage.cs) into a simple small project. the report can generate successfully.so seems it is not related with the specific file but with the entire project.I cannot find any useful info from /sonarqube-7.9.1/logs/ directory.Do you have the debug version or tell me how to turn on the log info.

…

------------------ 原始邮件 ------------------ 发件人: "Alexis Chatillon"<[email protected]>; 发送时间: 2019年10月25日(星期五) 下午3:44 收件人: "lequal/sonar-cnes-report"<[email protected]>; 抄送: "伦文叙"<[email protected]>;"Mention"<[email protected]>; 主题: Re: [lequal/sonar-cnes-report] Exception in thread "main"java.lang.NumberFormatException: For input string: "AboveAverage.cs" (#86) Hi @astrasia, Just a quick reminder. In order to investigate, we really need an example file that triggers this error. Thanks ! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[difeijin]

all the plugin installed. Chinese Pack 1.29,Findbugs 3.11.0,Git 1.8 (build 1574),GitHub Authentication for SonarQube 1.5 (build 870),JaCoCo 1.0.2 (build 475),LDAP 2.2 (build 608),SAML 2.0 Authentication for SonarQube 1.1.0 (build 181),SonarC# 7.15 (build 8572),SonarCSS 1.1.1 (build 1010),SonarFlex 2.5.1 (build 1831),SonarGo 1.1.1 (build 2000),SonarHTML 3.1 (build 1615),SonarJS 5.2.1 (build 7778),SonarJava 5.14 (build 18788),SonarKotlin 1.5.0 (build 315),SonarPHP 3.2.0.4868,SonarPython 1.14.1 (build 3143),SonarQube CNES Report 3.1.0,SonarRuby 1.5.0 (build 315),SonarScala 1.5.0 (build 315),SonarTS 1.9 (build 3766),SonarVB 7.15 (build 8572),SonarXML 2.0.1 (build 2020),Svn 1.9.0.1295,Xanitizer 2.0.0, http://192.168.1.240:9000/api/cnesreport/report?key=xxx&author=Administrator&token=xxx&generation=Generate {"errors":[{"msg":"For input string: \"AboveAverage.cs\""}]}

…

------------------ 原始邮件 ------------------ 发件人: "Benoît Garçon"<[email protected]>; 发送时间: 2019年10月7日(星期一) 凌晨0:16 收件人: "lequal/sonar-cnes-report"<[email protected]>; 抄送: "伦文叙"<[email protected]>;"Mention"<[email protected]>; 主题: Re: [lequal/sonar-cnes-report] Exception in thread "main"java.lang.NumberFormatException: For input string: "AboveAverage.cs" (#86) Hello @astrasia, Could you send us the content of 404.php, or a piece of project with which we can reproduce thius error? Thanks. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[Eduardx05]

I reproduce the error.

When we extract the component_tree measures in the Component provider. The getMinMetric and the getMaxMetric try to parse the file name of the component tree to double.

I saw that type of error on files that has numbers on the file name.

404.jsp
3A

1E

I change the next methods:

 private double getMinMetric(String metric){
        double min = Double.MAX_VALUE;
        for(Map c: componentsList){
            final String rawValue = (String)c.get(metric);
            if(rawValue!=null){
                try{
                    min = Math.min(min, Double.valueOf(rawValue));
                }catch(NumberFormatException e){
                    LOGGER.warning(metric +" : "+rawValue+" | Error Min" );
                    min = 0;
                }
                
            }
        }
        return min;
    }

    /**
     * Get max value for a specified metrics
     * */
    private double getMaxMetric(String metric){
        double max = -Double.MAX_VALUE;
        for(Map c: componentsList){
            final String rawValue = (String)c.get(metric);
            if(rawValue!=null){
                

                try{
                    max = Math.max(max, Double.valueOf(rawValue));
                }catch(NumberFormatException e){
                    LOGGER.warning(metric +" : "+rawValue+" | Error Max" );
                    max = 0;
                }
            }
        }
        return max;
    }

And then the reports generated.

[difeijin]

thanks,good work, expect the&nbsp; fix.

…

------------------&nbsp;原始邮件&nbsp;------------------ 发件人:&nbsp;"Eduardx05"<[email protected]&gt;; 发送时间:&nbsp;2020年4月13日(星期一) 中午12:06 收件人:&nbsp;"lequal/sonar-cnes-report"<[email protected]&gt;; 抄送:&nbsp;"伦文叙"<[email protected]&gt;;"Mention"<[email protected]&gt;; 主题:&nbsp;Re: [lequal/sonar-cnes-report] Exception in thread "main" java.lang.NumberFormatException: For input string: "AboveAverage.cs" (#86) I reproduce the error. When we extract the component_tree measures in the Component provider. The getMinMetric and the getMaxMetric try to parse the file name of the component tree to double. I saw that type of error on files that has numbers on the file name. 404.jsp 3A 1E I change the next methods: private double getMinMetric(String metric){ double min = Double.MAX_VALUE; for(Map c: componentsList){ final String rawValue = (String)c.get(metric); if(rawValue!=null){ try{ min = Math.min(min, Double.valueOf(rawValue)); }catch(NumberFormatException e){ LOGGER.warning(metric +" : "+rawValue+" | Error Min" ); min = 0; } } } return min; } /** * Get max value for a specified metrics * */ private double getMaxMetric(String metric){ double max = -Double.MAX_VALUE; for(Map c: componentsList){ final String rawValue = (String)c.get(metric); if(rawValue!=null){ try{ max = Math.max(max, Double.valueOf(rawValue)); }catch(NumberFormatException e){ LOGGER.warning(metric +" : "+rawValue+" | Error Max" ); max = 0; } } } return max; } And then the reports generated. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Sancretor]

Hi @Eduardx05 !

Thanks for your feedback and contribution, we truly appreciate it !
We're also glad you managed to reproduce this error... that was a tricky one.
I can't say when, but be sure I'll look into it as soon as possible.

[jeritiana]

I stumbled upon this issue too and I needed badly to generate a report lol

You have to be lucky to reproduce this on your side. It happens inside src/main/java/fr/cnes/sonar/report/providers/ComponentProvider.java, when the very first component value used inside isCountableMetric(String metric) is actually a valid number.

Here is a typical component and its attributes:

{Path=include/fieldbus/488, complexity=0, duplicated_lines_density=0.0, cognitive_complexity=0, ncloc=41, ID=AXTj4p-qHIPsNopKiPtX, comment_lines_density=42.3, Name=488}

488 in this particular case means IEEE-488 or GPIB field bus.

When calling isCountableMetric("Name"): the first non-null value is used to detect if the metric is countable, and NumberUtils.isCreatable("488") is indeed TRUE!

Then, the metric Name is also computed for all components in getMetricStats(), calling getMinMetric(String metric) and getMaxMetric(String metric), as reported by @Eduardx05, leading to the java.lang.NumberFormatException on all file names and directory names. The suggested fix pointed me to this analysis, but it is too late during the runtime.

Fix idea: exclude known attributes not to be in the computed metrics, such as Name or Path, not relying on their value. This will give a deterministic behavior, independently from the component order or name.

At least, that's what I found and it works on my setup.

Associated PR #179

[Sancretor]

Hi @jeritiana

Thanks a lot or your contribution !
That was a tricky one indeed.
We will have a look at your PR as soon as possible, as it would be great to merge it for the next 3.3.0 release.