Closed jasonm23 closed 8 months ago
Internal ticket created : TS-549
Seems to be an issue in
MathUtils.ParseIntOps.toIntOrMaxValue
Use of toLong
will only handle 64bit (max ≤19 digits), time for BigInteger
?
Currently working around this by replacing > 2,147,483,647 with 2,147,483,647 in coverage.lcov
Hi Jason,
Thanks for reaching our community!
While the fix you proposed is good for the tool itself, we are passing that information to other internal components and it requires other changes as well.
I am passing the internal ticket to the corresponding team. Keep in mind that this is a low priority for now.
Best, Stefan
we are passing that information to other internal components and it requires other changes as well.
Such as?
You have components that want an int overflow?
Facepalm moment
@jasonm23 Clearly there was some misunderstanding of the problem on our side. I answered in your PR thread. I used your PR as the starting point to fix the problem and to fix a bug that comes out when you handle such big numbers (you can't sum as easily as before, since you have overflows). I also added a test case. I will merge #479 (which contains your commit as well) when the CI is green.
Great to hear. Looking forward to the fix shipping
Expected Behavior
Parsing of
coverage.lcov
report.RipGrep shows the number which breaks the reporter.
Actual Behavior
Error stacktrace:
Reproducible Test Case
I assume parsing a report containing an Int value larger n will throw the error.