Fix stderr logging level in CommandExecutor

[t0mdavid-m]

Summary

Changed the logging level for stderr output from level 2 to level 0 in the CommandExecutor's stderr reader.

Changes

• Updated CommandExecutor.read_stderr() to log stderr messages at level 0 instead of level 2
• This ensures stderr output is captured with the correct logging priority

Details

The stderr logging level has been adjusted from 2 to 0. This change likely addresses an issue where stderr messages were being logged at an inappropriate verbosity level, potentially causing them to be filtered out or not displayed with the correct priority depending on the logging configuration.

https://claude.ai/code/session_01L9vBwhCPsXUTTxen3sW8rn

Summary by CodeRabbit

• Bug Fixes
  • Improved error logging visibility during command execution to better capture and display system errors.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

📝 Walkthrough

Walkthrough

The logging level for STDERR output in the read_stderr method was changed from level 2 to level 0 in CommandExecutor.py. This adjustment alters the severity at which stderr messages are logged while preserving all existing control flow and logic.

Changes

Cohort / File(s)	Summary
Logging Level Adjustment src/workflow/CommandExecutor.py	Modified read_stderr method to log STDERR lines at level 0 instead of level 2

Poem

🐰 A whisper in the logs so clear,
Where errors now ring bright and dear,
Level zero brings the news to light,
The rabbit hops with pure delight!
More visibility, less delay,
Stderr shines brighter every day!

✨ Finishing touches

• 📝 Generate docstrings

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}