-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
just adding logging in staging #3901
Conversation
Caution Review failedThe pull request is closed. 📝 Walkthrough📝 WalkthroughWalkthroughThe changes primarily involve enhancements to the Changes
Possibly related PRs
Suggested reviewers
Warning Rate limit exceeded@Baalmart has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 22 minutes and 21 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## staging #3901 +/- ##
===========================================
- Coverage 11.78% 11.77% -0.01%
===========================================
Files 114 114
Lines 15267 15277 +10
Branches 274 274
===========================================
Hits 1799 1799
- Misses 13468 13478 +10
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
src/device-registry/models/Event.js (2)
2790-2795
: Ensure logging is environment-specificThe added logging statements are helpful for debugging in the staging environment. To prevent unnecessary logging in production, consider wrapping these logs with an environment check so they execute only in staging.
2902-2916
: Consider conditional logging for productionThe additional log statements provide valuable debugging information. However, excessive logging in a production environment can lead to performance issues and cluttered logs. It's advisable to conditionally enable these logs based on the environment to ensure they are active only in staging.
Device registry changes in this PR available for preview here |
Device registry changes in this PR available for preview here |
Description
just adding logging in staging
Summary by CodeRabbit
New Features
Bug Fixes