Skip to content

docs: narrow engine#418's root cause further (round 47) - #442

Merged
tannevaled merged 1 commit into
mainfrom
narrow-engine418-round47
Nov 15, 2026
Merged

tannevaled merged 1 commit into
mainfrom
narrow-engine418-round47

Conversation

@tannevaled

Copy link
Copy Markdown
Contributor

Summary

  • Round 47 investigation of engine#418 (every localized string on github.com's own Support app renders as i18next's own object-fallback message).
  • Built a real React + ReactDOM + i18next + i18next-http-backend + react-i18next reconciliation inside this engine with a real async backend delay: it resolves correctly. This disproves round 36's theory ("react-i18next + settle-quiescence timing").
  • Patched the REAL, currently-served GitHub chunk with console.log probes and rendered the real page end to end (engine.Render against the live support.github.com/request/landing, via a custom http.RoundTripper substituting only that one chunk's bytes). For all 58 real t() calls the page makes, i18next's own resolve() returns the caller's OWN options object as the "resolved" value, without ever calling the real ResourceStore.getResource — traced to a specific call site inside resolve() that never fires, for a reason not yet isolated. The most likely engine-level theory (a nested function's var accumulator leaking an outer binding) was tested in isolation and ruled out.
  • No production code changed — pure investigation, documented honestly per this repo's own established precedent (rounds 94/103/117, 35, 36) for a lead too large to force into an unverified fix this round.

Test plan

  • go build ./... / go vet ./... clean (nothing in the engine itself changed)
  • git status --porcelain empty before this commit (all scratch probes, patched chunk copies, and the temporary driver program deleted after use)
  • FIDELITY.md's Known-gaps bullet for engine#418 updated to match

🤖 Generated with Claude Code

Instrument the real, currently-served GitHub Support chunk and render the
real page end to end: i18next's resolve() returns the caller's own options
object without ever calling the real ResourceStore.getResource, disproving
round 36's react-i18next/settle-timing theory along the way. Root cause
still open; no production code changed.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@tannevaled
tannevaled merged commit 7b3f8a1 into main Nov 15, 2026
13 checks passed
@tannevaled
tannevaled deleted the narrow-engine418-round47 branch November 15, 2026 21:42
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