json-repair 0.11.2 → 0.11.3

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 2d7b2f30c2451f62471beabed342ff8360f644e4ae703fa3e0f5490e44d4f0d1
-  data.tar.gz: 254abaa4ab104a0cc6650d02f099ebb00b0600ef213b00866da266159b6c1a37
+  metadata.gz: 69085d74f416811c4ac11ca7cfe2e9545a6cecdaeb32de96532932c99ab4aaf3
+  data.tar.gz: 4deee8e6715200ae693144a2c8cab914b9e8c78c3b539671f7632ce39d7b77f3
 SHA512:
-  metadata.gz: bfd417574888a7ff44a03870f48ab6e02c7bb7ae80189262e093425ba52e3943982f6ab36170c1cac6a3871e3d3379469b8319bbaa6defe8a0d473a7be6fe2a9
-  data.tar.gz: 208611ef2a09d4e3a5c91afe98334dfc7443a3db56de9624cfa82a3dea1e0c0480de18227646a96dac3c46f64af526e229f70dd9de4cd41cc1160a703b132a0b
+  metadata.gz: 31242bd165c070b1836d85a3fca120b5853a6e1ed715dbaeb75aa026563e033a7af491e318c119f3f3f899c4a7bb55382fc998372d7b55953358dc95d9c526be
+  data.tar.gz: b8a5a58a36d1c2b36922205f2b3b8d33e89e570fc215ed02ef288577a8d1325d96fa21cda9267ca78f44754b00a3150e5f6d149d6087c9f020e23090d47a13f2

data/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changes
 
+### 2026-06-12 (0.11.3)
+
+* Fix infinite recursion (`SystemStackError`) on a quoted string
+  followed by a backslash-escaped delimiter, like `["y"\, "z"]`. The
+  missing-end-quote retry in `parse_string` stops at the comma it
+  detected in the first pass, but the invalid-escape repair consumed
+  `\,` as one two-character step, jumping over the stop index and
+  re-firing the retry with identical arguments forever — violating the
+  contract that `JSONRepairError` is the only error raised. The escaped
+  delimiter now ends the string there and the dangling backslash is
+  dropped (the standard invalid-escape repair): `["y"\, "z"]` →
+  `["y\"","z"]`. The stop-index check is also hardened from `==` to
+  `>=` so no future multi-character advance can step over it and
+  recurse. Deliberate divergence from upstream
+  [jsonrepair](https://github.com/josdejong/jsonrepair), which crashes
+  with "Maximum call stack size exceeded" on the same input as of
+  v3.14.0 (still its latest release). Found by differential fuzzing
+  during the 0.11.2 work and re-validated the same way: across a
+  240-input grid of escape-adjacent shapes, only previously-crashing
+  inputs changed behavior — object shapes like `{"k": "y"\, "z"}` now
+  raise the same "Colon expected" as their backslash-free analog
+  `{"k": "y", "z"}`. Benchmarks flat vs 0.11.2.
+
 ### 2026-06-12 (0.11.2)
 
 * Fix the 0.11.0 doubled-colon repair silently mangling objects with a

data/lib/json/repair/version.rb

@@ -2,6 +2,6 @@
 
 module JSON
   module Repair
-    VERSION = '0.11.2'
+    VERSION = '0.11.3'
   end
 end

data/lib/json/repairer.rb

@@ -463,7 +463,13 @@ module JSON
           return true
         end
 
-        if @index == stop_at_index
+        # >= with a sentinel guard, not ==. Divergence from upstream (which
+        # compares with == as of v3.14.0): a multi-character advance below
+        # can step over the stop index, and resuming the comma-path retry
+        # from beyond it would re-fire that retry with identical arguments
+        # forever. The invalid-escape repair below avoids the only known
+        # overshoot; this is the backstop guaranteeing termination.
+        if stop_at_index >= 0 && @index >= stop_at_index
           # use the stop index detected in the first iteration, and repair end quote
           str = insert_before_last_whitespace(str, '"')
           @output << str
@@ -569,6 +575,15 @@ module JSON
             # repair a backslash escaped newline (like in Bash scripts)
             str << '\n'
             @index += 2
+          elsif @index + 1 == stop_at_index
+            # repair invalid escape character: remove it — but the escaped
+            # character is the delimiter the comma-path retry said to stop
+            # at, so drop only the backslash and let the stop check above
+            # fire there, keeping the delimiter a delimiter. Divergence
+            # from upstream, which consumes both characters, jumps the stop
+            # index, and crashes ("Maximum call stack size exceeded" on
+            # inputs like `["y"\, "z"]` as of v3.14.0).
+            @index += 1
           else
             # repair invalid escape character: remove it
             str << char

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: json-repair
 version: !ruby/object:Gem::Version
-  version: 0.11.2
+  version: 0.11.3
 platform: ruby
 authors:
 - Aleksandr Zykov