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

CLI: log to stderr instead of stdout #8784

Merged
merged 1 commit into from
Dec 6, 2024
Merged

Conversation

SpecLad
Copy link
Contributor

@SpecLad SpecLad commented Dec 6, 2024

Motivation and context

Since the ls command produces machine-readable output, we need to ensure that any log messages produced do not corrupt that output.

Logging to stderr is also conventional; Python's StreamHandler even defaults to it.

This breaks the import command tests, because previously they were looking at the last log message. I don't think we should be testing log messages, so add a proper print to this command. This also makes it consistent with the create command.

How has this been tested?

Unit tests.

Checklist

  • I submit my changes into the develop branch
  • I have created a changelog fragment
  • [ ] I have updated the documentation accordingly
  • [ ] I have added tests to cover my changes
  • [ ] I have linked related issues (see GitHub docs)
  • [ ] I have increased versions of npm packages if it is necessary
    (cvat-canvas,
    cvat-core,
    cvat-data and
    cvat-ui)

License

  • I submit my code changes under the same MIT License that covers the project.
    Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

  • New Features

    • Enhanced logging behavior in the command-line interface, now directing log messages to standard error (stderr) for better user experience during CLI operations.
    • Improved feedback for the TaskImport command by displaying the created task ID after task creation.
  • Bug Fixes

    • No bug fixes were made in this release.
  • Documentation

    • Updated changelog to reflect recent changes in logging behavior and task feedback.

Copy link
Contributor

coderabbitai bot commented Dec 6, 2024

Walkthrough

The changes in this pull request focus on modifying the logging behavior of the command-line interface (CLI) and enhancing the output of task creation feedback. Specifically, log messages are now directed to standard error (stderr) instead of standard output (stdout). Additionally, the TaskImport class's execute method has been updated to store and print the created task ID after importing from a backup, improving clarity in user feedback. Other aspects of the code remain unchanged, maintaining overall functionality.

Changes

File Path Change Summary
changelog.d/20241206_135902_roman_cli_logging.md Documentation of changes regarding logging output stream modification from stdout to stderr.
cvat-cli/src/cvat_cli/_internal/commands.py Updated TaskImport.execute method to store and print the created task ID for clarity.
cvat-cli/src/cvat_cli/_internal/common.py Modified configure_logger function to change logging output from sys.stdout to sys.stderr.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CLI
    participant TaskImport

    User->>CLI: Execute task import
    CLI->>TaskImport: Call execute method
    TaskImport->>TaskImport: Create task from backup
    TaskImport-->>CLI: Return created task
    CLI->>User: Print created task ID
Loading

🐇 "In the realm of code where rabbits hop,
Logs now dance where errors stop.
Task IDs gleam with a clearer light,
As stderr sings through day and night.
With each change, we leap and play,
In the CLI garden, bright and gay!" 🐇


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 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.

Since the `ls` command produces machine-readable output, we need to ensure
that any log messages produced do not corrupt that output.

Logging to stderr is also conventional; Python's `StreamHandler` even
defaults to it.

This breaks the `import` command tests, because previously they were looking
at the last log message. I don't think we should be testing log messages, so
add a proper `print` to this command. This also makes it consistent with the
`create` command.
Copy link

sonarqubecloud bot commented Dec 6, 2024

@SpecLad SpecLad marked this pull request as ready for review December 6, 2024 12:01
@SpecLad SpecLad requested a review from nmanovic as a code owner December 6, 2024 12:01
@SpecLad SpecLad requested a review from zhiltsov-max December 6, 2024 12:02
Copy link
Contributor

@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: 0

🧹 Outside diff range and nitpick comments (1)
cvat-cli/src/cvat_cli/_internal/commands.py (1)

421-426: LGTM! Minor formatting suggestion.

The changes improve output consistency with other commands and properly capture the task creation result. Consider removing the redundant string "ID" to match the exact format used in TaskCreate.

-        print(f"Created task ID", task.id)
+        print("Created task id", task.id)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between b5c0971 and 44d6397.

📒 Files selected for processing (3)
  • changelog.d/20241206_135902_roman_cli_logging.md (1 hunks)
  • cvat-cli/src/cvat_cli/_internal/commands.py (1 hunks)
  • cvat-cli/src/cvat_cli/_internal/common.py (1 hunks)
✅ Files skipped from review due to trivial changes (2)
  • cvat-cli/src/cvat_cli/_internal/common.py
  • changelog.d/20241206_135902_roman_cli_logging.md

@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 73.93%. Comparing base (ebe3dd6) to head (44d6397).
Report is 3 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8784      +/-   ##
===========================================
+ Coverage    73.92%   73.93%   +0.01%     
===========================================
  Files          409      409              
  Lines        43944    43945       +1     
  Branches      3985     3985              
===========================================
+ Hits         32485    32492       +7     
+ Misses       11459    11453       -6     
Components Coverage Δ
cvat-ui 78.37% <ø> (+0.02%) ⬆️
cvat-server 70.13% <100.00%> (+<0.01%) ⬆️

@SpecLad SpecLad merged commit ca3d700 into cvat-ai:develop Dec 6, 2024
43 of 44 checks passed
@SpecLad SpecLad deleted the cli-logging branch December 6, 2024 12:58
@cvat-bot cvat-bot bot mentioned this pull request Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants