Skip to content
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 to file ~/.local/state/hivemind/core.log #54

Merged
merged 2 commits into from
Feb 16, 2025
Merged

Conversation

JarbasAl
Copy link
Member

@JarbasAl JarbasAl commented Feb 16, 2025

Summary by CodeRabbit

  • New Features
    • Introduced command-line options for configuring logging behavior.
    • Users can now set the logging level, with a default of DEBUG.
    • Added the ability to specify a destination for log files, improving log management.

Copy link

coderabbitai bot commented Feb 16, 2025

Walkthrough

The update introduces command-line argument parsing into the HiveMind core. A new function parse_args() has been added to handle arguments for logging configuration, specifically --log-level and --log-path. The main() function now invokes parse_args() to determine the logging settings, applying default values when arguments are not provided. Additionally, a conditional log message indicates whether logs are directed to stdout or saved to a file.

Changes

File(s) Change Summary
hivemind_core/main.py Added parse_args() for command-line argument parsing; updated main() to configure logging using --log-level and --log-path; added conditional logging message

Sequence Diagram(s)

sequenceDiagram
    participant CLI as Command Line
    participant Main as main()
    participant Parser as parse_args()
    participant Logger as Logging Config

    CLI->>Main: Start program with arguments
    Main->>Parser: call parse_args()
    Parser-->>Main: Return logging level and log path
    Main->>Logger: Configure logging based on arguments
    Logger-->>Main: Logging configured
    Main->>Logger: Log message indicating output destination
Loading

Poem

I'm a rabbit hoppy and keen,
New commands make our logs serene.
Arguments parsed with carrot might,
Logging set just right tonight.
Leaping through code with a joyful sight!
🐇🥕✨

✨ Finishing Touches
  • 📝 Generate Docstrings (Beta)

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@JarbasAl JarbasAl requested a review from goldyfruit February 16, 2025 00:20
@JarbasAl JarbasAl marked this pull request as ready for review February 16, 2025 00:21
@JarbasAl JarbasAl merged commit e623ec2 into dev Feb 16, 2025
2 checks passed
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6967be9 and 2da0c6b.

📒 Files selected for processing (1)
  • hivemind_core/__main__.py (1 hunks)
🔇 Additional comments (3)
hivemind_core/__main__.py (3)

1-4: LGTM!

The imports are well-organized and include all necessary modules for the new logging functionality.


28-31: LGTM!

The log messages clearly indicate where users can find the logs, which improves user experience.


26-26:

❓ Verification inconclusive

Verify the log file path matches the PR objective.

The log file path construction using xdg_state_home() should resolve to ~/.local/state/hivemind/core.log.

Run this script to verify the path resolution:


🏁 Script executed:

#!/bin/bash
# Description: Verify that xdg_state_home resolves to ~/.local/state

# Test: Check if the module correctly resolves the path
python3 -c "from ovos_utils.xdg_utils import xdg_state_home; import os; print(os.path.join(xdg_state_home(), 'hivemind', 'core.log'))"

Length of output: 272


Log File Path Verification – Manual Check Required

The automated verification script didn’t produce the expected output due to a ModuleNotFoundError for ovos_utils. This prevents us from confirming that xdg_state_home() resolves to ~/.local/state/hivemind/core.log as intended. Please manually verify the following:

  • Ensure that the ovos_utils dependency is correctly installed or available in the environment.
  • Confirm that xdg_state_home() returns ~/.local/state so that the full path becomes ~/.local/state/hivemind/core.log.
  • Validate that the log configuration in hivemind_core/__main__.py matches the PR objective.

Comment on lines +8 to +12
def parse_args():
parser = argparse.ArgumentParser(description="Run the HiveMind service.")
parser.add_argument('--log-level', type=str, default="DEBUG", help="Set the logging level (e.g., DEBUG, INFO, ERROR).")
parser.add_argument('--log-path', type=str, default=None, help="Set the directory path for logs.")
return parser.parse_args()
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Add validation for log level values.

The function should validate that the provided log level is one of the standard Python logging levels.

Apply this diff to add validation:

 def parse_args():
     parser = argparse.ArgumentParser(description="Run the HiveMind service.")
-    parser.add_argument('--log-level', type=str, default="DEBUG", help="Set the logging level (e.g., DEBUG, INFO, ERROR).")
+    parser.add_argument('--log-level', type=str.upper, choices=['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'],
+                       default="INFO", help="Set the logging level.")
     parser.add_argument('--log-path', type=str, default=None, help="Set the directory path for logs.")
     return parser.parse_args()
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
def parse_args():
parser = argparse.ArgumentParser(description="Run the HiveMind service.")
parser.add_argument('--log-level', type=str, default="DEBUG", help="Set the logging level (e.g., DEBUG, INFO, ERROR).")
parser.add_argument('--log-path', type=str, default=None, help="Set the directory path for logs.")
return parser.parse_args()
def parse_args():
parser = argparse.ArgumentParser(description="Run the HiveMind service.")
parser.add_argument('--log-level', type=str.upper, choices=['DEBUG', 'INFO', 'WARNING', 'ERROR', 'CRITICAL'],
default="INFO", help="Set the logging level.")
parser.add_argument('--log-path', type=str, default=None, help="Set the directory path for logs.")
return parser.parse_args()

Comment on lines +22 to +27
# Set log path if provided, otherwise use default
if args.log_path:
LOG.base_path = args.log_path
else:
LOG.base_path = os.path.join(xdg_state_home(), "hivemind")

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Ensure log directory exists and handle potential errors.

The code should create the log directory if it doesn't exist and handle potential file system errors.

Apply this diff to add directory creation and error handling:

     # Set log path if provided, otherwise use default
+    try:
         if args.log_path:
             LOG.base_path = args.log_path
         else:
             LOG.base_path = os.path.join(xdg_state_home(), "hivemind")
+        if LOG.base_path != "stdout":
+            os.makedirs(LOG.base_path, exist_ok=True)
+    except OSError as e:
+        LOG.error(f"Failed to create log directory: {e}")
+        LOG.base_path = "stdout"
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
# Set log path if provided, otherwise use default
if args.log_path:
LOG.base_path = args.log_path
else:
LOG.base_path = os.path.join(xdg_state_home(), "hivemind")
# Set log path if provided, otherwise use default
try:
if args.log_path:
LOG.base_path = args.log_path
else:
LOG.base_path = os.path.join(xdg_state_home(), "hivemind")
if LOG.base_path != "stdout":
os.makedirs(LOG.base_path, exist_ok=True)
except OSError as e:
LOG.error(f"Failed to create log directory: {e}")
LOG.base_path = "stdout"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant