feat: install the SolidSyslog error handler - #29
Merged
Conversation
Nothing in the library fails loudly. A _Create that cannot succeed returns a Null object and carries on, 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 +404 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 range, not the text. That is 404 bytes for something this device may never use. It buys the difference between a silent failure and a sentence, which is worth more than the bytes on anything that has to be trusted to report. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
📝 WalkthroughWalkthroughThe application adds a syslog error handler module, registers it before object creation, includes it in the baseline build, and updates documentation and measurement reports for the new error-handler stage. ChangesSyslog error handler
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant main
participant SyslogErrorHandler
participant SolidSyslog
participant Console
main->>SyslogErrorHandler: Install before first _Create
SyslogErrorHandler->>SolidSyslog: Register OnSyslogError
SolidSyslog->>SyslogErrorHandler: Report error event
SyslogErrorHandler->>Console: Print formatted error
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@run-report.md`:
- Around line 52-62: Update the Self-check results in run-report.md so
measurements only receive “OK” when actual and expected values match exactly;
otherwise report a mismatch or fail the check. Regenerate
measurements/error-handler.csv and the report from the same build so
mbedtls_peak, mbedtls_free, and lwip_pbufs_free no longer show inconsistent
values as successful.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: c6162096-2a8e-42b7-8ce9-5f8f85495da8
⛔ Files ignored due to path filters (2)
measurements/error-handler.csvis excluded by!**/*.csvmeasurements/stages.tsvis excluded by!**/*.tsv
📒 Files selected for processing (6)
CMakeLists.txtREADME.mdapp/main.capp/syslog/SyslogErrorHandler.capp/syslog/SyslogErrorHandler.hrun-report.md
This was referenced Jul 29, 2026
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
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.
Pull request
What this stage adds
Nothing in the library fails loudly. A _Create that cannot succeed returns a Null
object and carries on, 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 +404 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 range, not the text.
That is 404 bytes for something this device may never use. It buys the
difference between a silent failure and a sentence, which is worth more than the
bytes on anything that has to be trusted to report.
Files
Checklist
measurements/error-handler.csvcommitted.measurements/stages.tsv.python3 scripts/gen-cost-table.py../run.shgreen (build + QEMU + baseline self-check) —run-report.mdcommitted.Context for review: 2 of 21 sequential single-commit PRs replaying the integration on top of the Baseline root. Each lands green and reviewed before the next is built on it, because a change to an early commit would force every commit above it to be re-run and re-measured.
Summary by CodeRabbit
New Features
Documentation