use --refresh-toolsets instead of toolset refresh in the log - #700
Conversation
WalkthroughA logging message in the Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Note ⚡️ Unit Test Generation is now available in beta!Learn more here, or try it out under "Finishing Touches" below. ✨ Finishing Touches
🧪 Generate unit tests
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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.
Actionable comments posted: 0
🧹 Nitpick comments (1)
holmes/core/toolset_manager.py (1)
293-294: Clarify invocation context for the new flagThe phrasing “To refresh: use flag
--refresh-toolsets” is slightly opaque to users skimming logs—they still need to know which Holmes command this flag belongs to. A more self-contained message improves UX and avoids support questions.- f"Using {num_available_toolsets} datasources (toolsets). To refresh: use flag `--refresh-toolsets`" + f"Using {num_available_toolsets} datasources (toolsets). " + f"Re-run the CLI with the `--refresh-toolsets` flag to refresh."(Keep the f-string on one line if you prefer; line-split here only for diff clarity.)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
holmes/core/toolset_manager.py(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: llm_evals
- GitHub Check: Pre-commit checks
- GitHub Check: Pre-commit checks
No description provided.