FA-3071 / Serialization / Open access
Non-ASCII diagnostic characters remain literal · case 01
Non-ASCII diagnostic characters remain literal.
ROOT CAUSE
The implementation applies an operation whose text or grammar semantics violate this contract: Return ASCII-only repr with standard backslash escapes.
THE FAILURE
The implementation applies an operation whose text or grammar semantics violate this contract: Return ASCII-only repr with standard backslash escapes.
Unsuccessful approach: The attempted repair handles the primary example but still violates a separate boundary of the same contract.
Case contract
Return ASCII-only repr with standard backslash escapes.
Why this case matters
A local executable model for consumers of structured text; oracle values are authored literals, not outputs copied from the repaired implementation.
1 / The failure
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
import re, unicodedata, json, csv, io, html, base64, binascii, codecs, struct
from urllib.parse import quote, unquote, unquote_to_bytes, urlencode, parse_qsl, urlsplit, urlunsplit
from email.header import decode_header, make_header
from email.utils import getaddresses
from xml.etree import ElementTree as ET
import shlex, string, textwrap
N = 1
observations = []
def solve(x):
try:
return repr(x)
except Exception as exc:
return {"error": type(exc).__name__}
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('boundary 1', solve('é'), "'\\xe9'")
check('boundary 2', solve('😀'), "'\\U0001f600'")
check('boundary 3', solve('a'), "'a'")
check('boundary 4', solve('\n'), "'\\n'")
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| boundary 1 | 'é' | '\xe9' | Failed |
| boundary 2 | '😀' | '\U0001f600' | Failed |
| boundary 3 | 'a' | 'a' | Passed |
| boundary 4 | '\n' | '\n' | Passed |
SHA-256 / 6c2bcd76315e40a2e7117618aa08b81b7db1fc79c88a7f34ea33febf401d1637
2 / The unsuccessful fix
Exit 1"""Failure Map reference implementation. Python standard library only."""
import json
import re, unicodedata, json, csv, io, html, base64, binascii, codecs, struct
from urllib.parse import quote, unquote, unquote_to_bytes, urlencode, parse_qsl, urlsplit, urlunsplit
from email.header import decode_header, make_header
from email.utils import getaddresses
from xml.etree import ElementTree as ET
import shlex, string, textwrap
N = 1
observations = []
def solve(x):
try:
return repr(x.encode('unicode_escape').decode())
except Exception as exc:
return {"error": type(exc).__name__}
def check(label, actual, expected):
observations.append({"check": label, "actual": actual, "expected": expected, "passed": actual == expected})
check('boundary 1', solve('é'), "'\\xe9'")
check('boundary 2', solve('😀'), "'\\U0001f600'")
check('boundary 3', solve('a'), "'a'")
check('boundary 4', solve('\n'), "'\\n'")
print(json.dumps({"observations": observations, "passed": all(x["passed"] for x in observations)}, ensure_ascii=False))
raise SystemExit(0 if all(x["passed"] for x in observations) else 1)
| Boundary fixture | Actual | Expected | Outcome |
|---|---|---|---|
| boundary 1 | '\\xe9' | '\xe9' | Failed |
| boundary 2 | '\\U0001f600' | '\U0001f600' | Failed |
| boundary 3 | 'a' | 'a' | Passed |
| boundary 4 | '\\n' | '\n' | Failed |
SHA-256 / 7b02787dbf2e7e683cbed3ebb467534d344ff4a4b14e2fec34ffe8c4e7186c98
HELD IN THE MEMBER ARCHIVE
The verified repair and its recorded checks are member-only.
This mechanism has 4 recorded checks per implementation. The open-access tier publishes the failure and the unsuccessful fix; the repaired source that passes every check, and the observations that prove it, are available to members.
Every case sharing this mechanism uses the same contract and the same repair, so this one record is held back for all of them.
Member access is invitation-based. Sign in with your invited account to inspect the repair.
Sign in to the archive ↗Verification & scope
This reproducer isolates one failure mechanism. Results cover the supplied fixtures. Variants within a family share a test contract and should remain grouped when constructing evaluation splits. Related mechanisms with a shared evaluation_group must also remain together; these controlled models are not independent production incidents.
Observations recorded using Python 3.12.14 at 2026-09-29T14:37:20.820217+00:00.
Case digest / 0423b0556495aaceeba4ed1178304245c1f4aaf8f39b14cd61d69b3afd681ca5