fix: unify extract-log-errors output behavior for empty manifests#814
fix: unify extract-log-errors output behavior for empty manifests#814
Conversation
Ensure empty and non-empty log flows use the same output writer so --output behavior is consistent and path reporting is preserved. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe changes consolidate output handling in 🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Summary
This PR resolves #812 by unifying output handling in
scripts/extract-log-errors.pyso both empty and non-empty log sets flow throughemit_output(...).What changed
emit_empty_output(...).main()to:No log files found.on stderr when no logs are presentsummaryemit_output(summary, args.output)Tests
tests/test_extract_log_errors.pyto verify--outputprints the output path for both:/tmp/gh-aw/agent/venv/bin/python -m pytest -q tests/test_extract_log_errors.py(4 passed)Issue linkage
Closes #812.
The body of this PR is automatically managed by the Trigger Update PR Body workflow.