Fix entry duplication at beginning of file(s)#579
Merged
Conversation
Codecov Report
@@ Coverage Diff @@
## main #579 +/- ##
=======================================
Coverage ? 74.97%
=======================================
Files ? 133
Lines ? 10089
Branches ? 0
=======================================
Hits ? 7564
Misses ? 2060
Partials ? 465 Continue to review full report at Codecov.
|
|
FYI, on the open telemetry log collection repo, it is not flaky. |
jmwilliams89
approved these changes
Mar 8, 2022
cpheps
approved these changes
Mar 8, 2022
Contributor
cpheps
left a comment
There was a problem hiding this comment.
LGTM, Please update branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of Changes
Backporting a data duplication fix that was recently released in the OTEL repo. I don't have a great understanding of the complex file input operator, but I do know that the test being added (
TestIgnoreEmptyFiles) is flaky (fails most of the time) until the actual fix is implemented. Once the fix is in place, the new test passes 100% of the time for me.For more context around the issue:
Please check that the PR fulfills these requirements