fix: log Enode charger count at debug level instead of info#131
Conversation
This fires on every poll, so at info level it spams the log with a routine count instead of something a user needs to see by default.
|
Warning Review limit reached
Next review available in: 58 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 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 |
Handleiding voor reviewers (ingeklapt bij kleine PR's)Handleiding voor reviewersVerlaag het logniveau van routinematige Enode-laadpaaltelling van info naar debug om standaardlogs minder ruiserig te maken, terwijl gedetailleerde informatie over het ophalen van laadpalen beschikbaar blijft op debugniveau. Wijzigingen op bestandsniveau
Tips en commando'sInteractie met Sourcery
Je ervaring aanpassenGa naar je dashboard om:
Hulp krijgen
Original review guide in EnglishReviewer's guide (collapsed on small PRs)Reviewer's GuideLower the log level of routine Enode charger count messages from info to debug to avoid noisy default logs while keeping detailed charger fetch information available at debug level. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
There was a problem hiding this comment.
Hey - ik heb je wijzigingen bekeken en ze zien er geweldig uit!
Sourcery is gratis voor open source - als je onze reviews waardeert, overweeg dan om ze te delen ✨
Original comment in English
Hey - I've reviewed your changes and they look great!
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.



Summary
"%s Enode Chargers Found") was logged atinfolevel, but this fires on every poll — it's routine, expected output, not something a user needs surfaced by default.debug, consistent with the surrounding charger-fetch logging (the following line,"Enode Chargers data: %s", was already debug).Test plan
Samenvatting door Sourcery
Verbeteringen:
Original summary in English
Summary by Sourcery
Enhancements: