Skip to content

fix: escape non-ASCII chars as JSON.parse fallback in event parser#721

Merged
FL4TLiN3 merged 1 commit intomainfrom
fix/openai-e2e-parser-escape
Mar 5, 2026
Merged

fix: escape non-ASCII chars as JSON.parse fallback in event parser#721
FL4TLiN3 merged 1 commit intomainfrom
fix/openai-e2e-parser-escape

Conversation

@FL4TLiN3
Copy link
Contributor

@FL4TLiN3 FL4TLiN3 commented Mar 5, 2026

Summary

  • Add fallback in event parser: if JSON.parse fails, retry with non-ASCII chars escaped as Unicode sequences
  • Debug logging to verify escape approach works for the startRun event
  • Addresses OpenAI E2E test failure caused by em dashes in instruction text

Test plan

  • Check CI E2E to see if OpenAI provider test passes

When JSON.parse fails, retry with non-ASCII characters escaped as
Unicode sequences (\uXXXX) to work around JSC parse issues.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@FL4TLiN3 FL4TLiN3 enabled auto-merge (squash) March 5, 2026 00:43
@FL4TLiN3 FL4TLiN3 merged commit 96bfb18 into main Mar 5, 2026
11 checks passed
@FL4TLiN3 FL4TLiN3 deleted the fix/openai-e2e-parser-escape branch March 5, 2026 00:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant