-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
assume we receive logs by lines and don't ignore those without EOL #10660
Conversation
5954508
to
a027778
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
a027778
to
f7012e1
Compare
f7012e1
to
a71a3a6
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## v2 #10660 +/- ##
==========================================
- Coverage 59.79% 59.77% -0.02%
==========================================
Files 107 107
Lines 9481 9487 +6
==========================================
+ Hits 5669 5671 +2
- Misses 3232 3234 +2
- Partials 580 582 +2
☔ View full report in Codecov by Sentry. |
a71a3a6
to
38bb111
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Also 😂 I thought this sounded familiar: #8605 (comment)
38bb111
to
26a6109
Compare
Signed-off-by: Nicolas De Loof <[email protected]>
26a6109
to
1d15914
Compare
What I did
as we attach to containers we receive output as a low-level
Write([]byte)
that we split into lines to prepend container prefixif container log doesn't include an EOL character we won't dump it to logs
This PR assumes we don't get container output per character but as full lines (which is the case AFAICT) so that we dump logs as we receive them
Related issue
fixes #10658
(not mandatory) A picture of a cute animal, if possible in relation to what you did