Skip to content

feat: install the SolidSyslog error handler - #2

Merged
DavidCozens merged 1 commit into
mainfrom
stage-02-error-handler
Aug 16, 2026
Merged

feat: install the SolidSyslog error handler#2
DavidCozens merged 1 commit into
mainfrom
stage-02-error-handler

Conversation

@DavidCozens

Copy link
Copy Markdown
Contributor

Install the handler before any other call into SolidSyslog.

SolidSyslog_SetErrorHandler(OnSyslogError, NULL);

Nothing in the library fails loudly. A _Create that cannot succeed substitutes a Null object and
reports it rather than returning NULL, so a logger that has silently stopped looks exactly like
one with nothing to say. The handler is what tells the two apart, which is why it goes in before
the first _Create and not after something looks wrong. It reports many misconfiguration errors,
and can save significant time while integrating.

This is not only an integration aid. The handler is the seam into the device's own error and health
reporting, and it stays valuable at run time: later stages raise an edge-triggered warning when the
collector becomes unreachable and a notice when delivery recovers. Route it wherever the device
already routes faults — here, the same console as everything else, so a fault lands in the run
report next to the rest of what the device did.

The handler names the four lifecycle categories a misconfigured integration raises and prints the
rest numerically. A device reacting to a fault would switch on the category rather than the text.

When you need it. Every device, and first. It is the only thing standing between a
misconfigured logger and a silent one.

The build gains one source file and its include directory. Nothing about how SolidSyslog enters
the build changes.

@DavidCozens

Copy link
Copy Markdown
Contributor Author

@coderabbitai pause

@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown

Note

Reviews paused

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 34c425f9-b786-400a-8f14-264c3506f72c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

Comment @coderabbitai help to get the list of available commands.

@coderabbitai

coderabbitai Bot commented Aug 16, 2026

Copy link
Copy Markdown
✅ Action performed

Reviews paused.

Nothing in the library fails loudly. A _Create that cannot succeed substitutes a
Null object and reports it rather than returning NULL, so a logger that has
silently stopped looks exactly like one with nothing to say. The handler is what
tells them apart, and it goes in before the first _Create rather than after
something looks wrong.

  Flash  +412 B
  RAM      +8 B

The handler prints to the same console as everything else, so a fault lands in
the run report next to the rest of what the device did. It names the four
lifecycle categories a misconfigured integration raises and prints the rest
numerically — a device reacting to those would switch on the category, not the
text.

It is more than an integration aid. The handler is the seam into the device's own
error and health reporting, and later stages use it at run time: an edge-triggered
warning when the collector becomes unreachable, a notice when delivery recovers.

The build gains one source file and its include directory. Nothing about how
SolidSyslog enters the build changes.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@DavidCozens
DavidCozens force-pushed the stage-02-error-handler branch from b3ac316 to 697c5e2 Compare August 16, 2026 21:46
@DavidCozens
DavidCozens changed the base branch from stage-01-linked to main August 16, 2026 21:46
@DavidCozens
DavidCozens merged commit 4331c92 into main Aug 16, 2026
@DavidCozens
DavidCozens deleted the stage-02-error-handler branch August 16, 2026 21:54
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