Repository navigation
fix(ios): compile release diagnostics symbols - #10065
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughThe change makes diagnostic log injection and responder identity mapping available in release builds. Debug-only responder class-name helpers remain restricted to DEBUG builds. ChangesRelease diagnostics
Estimated code review effort: 2 (Simple) | ~10 minutes Mergeability Score: ⚪ Minimal · up to The change enables required release diagnostics support while keeping verbose probing debug-only; no actionable merge-blocking risk remains beyond normal checks and review. Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 25✅ Passed checks (25 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The internal TestFlight Release build failed on main because diagnostics call sites moved into Release while their responder helper and diagnostic log property remained DEBUG-only.
Make the shared responder identity mapper, diagnostic log sink, and shell-to-surface injection available in Release. Keep the verbose responder class-name probe DEBUG-only.
Validation: diff check passed; branch rebased onto current main. The local package-only build cannot typecheck iOS dependencies on macOS, and the full simulator graph was interrupted while resolving packages. Hosted checks are the source-of-truth for the Release compiler path.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by cubic
Fixes iOS Release build by compiling required diagnostics symbols in Release. Previously, diagnostics call sites were present in Release but the responder mapper, diagnostic log sink, and shell-to-surface injection were DEBUG-only; now these are available in Release, while the verbose responder class-name probe remains DEBUG-only. This enables structured diagnostics in Release without verbose logs.
GhosttySurfaceView.diagnosticLognow compiles in Release and remains optional; payloads are bounded and privacy-safe.TerminalInputTextView.responderIdentity(of:)is available in Release; the class-name readback helper stays DEBUG-only.GhosttySurfaceRepresentableinjects the diagnostic sink in Release; if the store does not provide one, probes no-op. No runtime behavior change beyond enabling structured diagnostic events.Written for commit 5799b88. Summary will update on new commits.
Summary by CodeRabbit