Skip to content

Conversation

@dariuszd21
Copy link
Contributor

@dariuszd21 dariuszd21 commented Apr 29, 2025

  • Have you followed the guidelines for contributing?
  • Have you signed the CLA?
  • Have you successfully run tox?

If streaming_brief=True is set for Emitter and there is log entry (log.info()) before message that has white space characters inside (e.g \n, \t), output is broken.

Signed-off-by: Dariusz Duda <dariusz.duda@canonical.com>
@codecov
Copy link

codecov bot commented Apr 29, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 93.97%. Comparing base (99394c9) to head (f250fcd).
Report is 79 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #338      +/-   ##
==========================================
+ Coverage   93.24%   93.97%   +0.73%     
==========================================
  Files           7       11       +4     
  Lines        1080     1395     +315     
  Branches      200      290      +90     
==========================================
+ Hits         1007     1311     +304     
- Misses         66       75       +9     
- Partials        7        9       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Signed-off-by: Dariusz Duda <dariusz.duda@canonical.com>
@dariuszd21 dariuszd21 force-pushed the work/logger-affects-progress branch from 2c24a17 to f250fcd Compare April 30, 2025 11:46
@dariuszd21 dariuszd21 changed the title Work/logger affects progress logger pollutes strings with white spaces May 6, 2025
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.

1 participant