Skip to content

fix(ci): repair invalid LLM JSON escapes in issue translation - #3

Closed
Wibias wants to merge 1 commit into
devfrom
fix/issue-translation-invalid-json-escapes
Closed

fix(ci): repair invalid LLM JSON escapes in issue translation#3
Wibias wants to merge 1 commit into
devfrom
fix/issue-translation-invalid-json-escapes

Conversation

@Wibias

@Wibias Wibias commented Jul 26, 2026

Copy link
Copy Markdown
Owner

Summary

  • Long Korean issue translation in run 30208536337 produced a complete English title/body, but JSON.parse failed on invalid \' escapes (Kiro\'s).
  • Parse step fail-closed with requires_translation=false, so Apply inline translation was skipped.
  • Repair invalid JS-style escapes inside JSON strings before parse; regression test mirrors that payload.

Test plan

  • node --test .github/scripts/parse-issue-translation-response.test.cjs
  • Replayed the failing job model response through the new parser → requires_translation: true
  • After merge, re-run Translate on the Korean Kiro 429 issue (workflow_dispatch) and confirm title/body update

gpt-4o-mini emits JS-style \' inside JSON strings; that made Parse AI response fail closed and skip Apply on long non-English issues.
@github-actions github-actions Bot added the bug Something isn't working label Jul 26, 2026
@Wibias

Wibias commented Jul 26, 2026

Copy link
Copy Markdown
Owner Author

Opened against the fork by mistake; recreating against lidge-jun/opencodex.

@Wibias Wibias closed this Jul 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant