After reading carefully issue #148, I have found that some factoids are affected by some transient metrics from OSSMETER that wrongly set a percentage of 14.29 (100/7) when the sum of data is zero. For example:
The problematic code comes from OSSMETER and was barely checked in Scava as the metrics were supposedly to be correct. Thus, I'm analyzing each transient metric for code that looks similar and fix the issue in the transient metrics. Which should fix the factoids. As well, I'm adding methods to deal with these changes in the factoids.
After reading carefully issue #148, I have found that some factoids are affected by some transient metrics from OSSMETER that wrongly set a percentage of 14.29 (100/7) when the sum of data is zero. For example:
At the beginning I though that only one metric was concerned and fixed with commit https://github.com/crossminer/scava/commit/3a95498638d7164a9ecb99334c4bbf7d90672b58. However, I have found more metrics that need to be fixed.
The problematic code comes from OSSMETER and was barely checked in Scava as the metrics were supposedly to be correct. Thus, I'm analyzing each transient metric for code that looks similar and fix the issue in the transient metrics. Which should fix the factoids. As well, I'm adding methods to deal with these changes in the factoids.