fix: warn when effect registration exceeds the list limit - #5837
fix: warn when effect registration exceeds the list limit#5837keeltrace wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. Walkthrough
ChangesEffect List Diagnostics
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to When the effect list is full, rejected effects now produce a debug warning with their metadata while retaining existing registration behavior. No current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
Fixes #5827.
When
WS2812FX::addEffect()reaches the 254-effect capacity, it currently returns255silently. Most usermods discard that return value, so dropped effects are difficult to diagnose.This adds a debug warning only on the full-list failure path and includes the effect metadata string that could not be registered. It intentionally does not change the 8-bit effect ID limit or overlap with the separate larger-effect-ID work.
Validation:
git diff --checkmainI could not run a firmware build locally because PlatformIO is not installed in this environment.
Summary by CodeRabbit