Fix missing_constant not suppressing min/max range errors in ASCII tables - #1664
Open
jordanpadams wants to merge 1 commit into
Open
Fix missing_constant not suppressing min/max range errors in ASCII tables#1664jordanpadams wants to merge 1 commit into
jordanpadams wants to merge 1 commit into
Conversation
…bles (#1660) In SpecialConstantChecker.sameContent(), BigDecimal values (used for ASCII_Real and other ASCII numeric field types) were being converted to Double then to a raw-bit-pattern BigInteger before comparison. When the constant representation is a decimal string like '-.99999', the code then called BigDecimal.equals(BigInteger), which always returns false, so missing_constant values were never recognized and the value was incorrectly compared against Field_Statistics min/max bounds. Fix: when the incoming Number is a BigDecimal and the constant representation is decimal, compare directly via BigDecimal.compareTo() before falling through to the IEEE 754 bit-pattern path. Also refactors the repr_decimal boolean into named intermediate variables (hasDecimalPoint, hasScientificNotation) for readability. Adds test case using pccds.xml/pccds.tab from the compil-comet dataset which exhibits the original failure. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
|
nutjob4life
reviewed
Aug 24, 2026
| // conversion that causes missing_constant values like "-.99999" to never match. | ||
| if (number instanceof BigDecimal && repr_decimal) { | ||
| BigDecimal constant = SpecialConstantBitPatternTransforms.asBigDecimal(constant_repr, radix); | ||
| return constant.compareTo((BigDecimal) number) == 0; |
Member
There was a problem hiding this comment.
Big thumbs-up for compareTo 🎉
nutjob4life
reviewed
Aug 24, 2026
Comment on lines
+188
to
+189
| boolean hasScientificNotation = (constant_repr.contains("E") || constant_repr.contains("e")) | ||
| && !constant_repr.startsWith("0x") && !constant_repr.startsWith("0X"); |
Member
There was a problem hiding this comment.
Note that the hexadecimal exclusion here applies only to scientific notation, not to the decimal-point test. That means something like 0x1.23 is still classified as repr_decimal.
This is not a regression, as the behavior already existed before this pull request. Maybe something to note for the future.
nutjob4life
requested changes
Aug 24, 2026
nutjob4life
left a comment
nutjob4life
left a comment
Member
There was a problem hiding this comment.
I'd go ahead and approve this as is (and the comments I interspersed in the code aren't deal-breakers), except the tests don't pass now:
[ERROR] Failures:
[ERROR] CucumberTest.Example #1.4: NASA-PDS/validate#1379-1 summary:totalWarnings ==> expected: <3> but was: <0>
[ERROR] CucumberTest.Example #1.65: NASA-PDS/validate#427-1 summary:totalWarnings ==> expected: <2> but was: <0>
[ERROR] CucumberTest.Example #1.8: NASA-PDS/validate#690-1 summary:totalWarnings ==> expected: <888> but was: <0>
[INFO]
[ERROR] Tests run: 327, Failures: 3, Errors: 0, Skipped: 0
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
I ran them twice just to make sure, but got the same failures.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🗒️ Summary
Fixes a bug where
missing_constant(and other special constants with decimal values) were not suppressingerror.table.field_value_out_of_min_max_rangeerrors in ASCII character/delimited/binary table fields.Root cause: In
SpecialConstantChecker.sameContent(), values arriving asBigDecimal(all ASCII numeric field types go throughNumberUtils.createBigDecimal()) were being convertedBigDecimal → Double → BigInteger(raw IEEE 754 bit pattern)before comparison. For a decimal constant like-.99999, the code then calledBigDecimal.equals(BigInteger), which is alwaysfalse, so the special constant was never recognized. The value then fell through to theField_Statisticsmin/max comparison and incorrectly triggered an error.Fix: Added an early-return path in
sameContent(): when the incomingNumberis aBigDecimaland the constant representation is decimal (contains.or scientific notatione/E), compare directly viaBigDecimal.compareTo()before the bit-pattern conversion path.Also refactors the
repr_decimalboolean into two named variables (hasDecimalPoint,hasScientificNotation) for readability per code review.⚙️ Test Data and/or Report
Added Cucumber scenario
1660-1using the real-worldpccds.xml/pccds.tabdataset from the compil-comet archive (linked in the issue). Before fix: 46error.table.field_value_out_of_min_max_rangeerrors. After fix: 0 errors, product passes.♻️ Related Issues
Fixes #1660
🤓 Reviewer Checklist