-
Notifications
You must be signed in to change notification settings - Fork 42
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
Log a warning when pending actions are skipped #840
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📝 WalkthroughWalkthroughThe pull request introduces a new warning log in the Possibly related PRs
Suggested reviewers
🪧 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 (
|
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 (1)
plane/src/controller/drone.rs (1)
168-170
: LGTM! Consider enhancing the warning message.The warning log is well-placed and appropriately uses the warn level to highlight potential missed actions.
Consider including the limit value in the message for better context:
- tracing::warn!(count, "Query returned the maximum number of pending actions; other pending actions may be missed."); + tracing::warn!( + count, + limit = pending_actions_limit, + "Query returned the maximum number of pending actions ({count}/{limit}); other pending actions may be missed." + );
No description provided.