fix(host): log SolarError fields, not the bare object#18
Merged
Conversation
`console.error("[solar]", err)` printed `[solar] [object Object]` in the
CEF console because SolarError is a plain `{ code, message, recoverable }`
object (not an Error) and the host's log bridge string-coerces the second
arg. That swallowed `code`/`message` and made the M3 black-screen
incident undiagnosable from the antenna logs.
Log the fields explicitly so the real cause always survives, in both the
host and dev bootstraps.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Merged
ClodoCapeo
added a commit
that referenced
this pull request
Jun 11, 2026
Legible host error logging (code: message) — Conduit #18. Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
During the M3 black-screen incident the antenna logs showed only
[solar] [object Object]— zero diagnostic signal. Proven cause:SolarErroris a plain{ code, message, recoverable }object (not anErrorsubclass), andconsole.error("[solar]", err)in the Pulsar CEF log bridge string-coerces the second arg, so every error code collapses to[object Object]. The string carries no information about which code fired (INVALID_VALUEvsBUNDLE_FETCH_FAILEDvsVERSION_GAPall look identical).This is what led the prior diagnosis to guess
whereEmptyN— the realcode/messagewere never visible.Fix
Log the fields explicitly in both the host and dev bootstraps:
No behaviour change beyond the log line; broadcast still surfaces no chrome.
🤖 Generated with Claude Code