You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@grails.apache.org by GitBox <gi...@apache.org> on 2026/09/01 11:43:34 UTC
[GH] (grails-core/fix/json-scanner-number-parsing): Workflow run "Code Style" is working again!
The GitHub Actions job "Code Style" on grails-core.git/fix/json-scanner-number-parsing has succeeded.
Run started by GitHub user borinquenkid (triggered by borinquenkid).
Head commit for run:
070707e354fbbe82aab511b5786371f27577cef2 / Walter Duque de Estrada <wb...@mac.com>
Fix JsonScanner number parsing for bare exponents and -Infinity
Two bugs found while adding test coverage for JsonReader/JsonWriter on
8.1.x, cherry-picked here since JsonScanner is unchanged since 7.0.x:
- SAW_EXPONENT_DIGITS was the only numeric scanner state whose
terminator switch omitted an explicit end-of-input case (every
sibling state treats EOF the same as a closing delimiter), so a
bare exponent-notation number with nothing following it (e.g. a
top-level "1e2") threw JsonParseException instead of parsing.
- SAW_MINUS_I appended the character it read on every iteration of
its "-Infinity" match loop, including the terminator character read
immediately after matching the literal's final 'y' - so the buffer
handed to Double.parseDouble always carried one extra trailing
character, and "-Infinity" failed to parse in every context
(end-of-input, before a comma, before a closing bracket).
This branch has no prior JsonReader test coverage, so a minimal
JsonReaderSpec is added here with just the two regression tests -
broader JsonReader/JsonWriter coverage exists only on 8.1.x.
Co-Authored-By: Claude Sonnet 5 <no...@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QAjfckcY4EJsxranv1RyGV
Report URL: https://github.com/apache/grails-core/actions/runs/33501407087
With regards,
GitHub Actions via GitBox