Skip to content
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

[FlowAggregator] Use correct input channel in flowExportLoopProxy #6990

Conversation

antoninbas
Copy link
Contributor

The code was invalid as the function was consuming messages straight from the collector instead of from the preprocessor, hence bypasing the preprocessor. This was not caught by e2e tests because the preprocessor output channel is small (capacity of 16), hence it was filling up very quickly and only a few uninteresting (i.e., irrelevant to the test cases) records were lost.

The code was invalid as the function was consuming messages straight
from the collector instead of from the preprocessor, hence bypasing the
preprocessor. This was not caught by e2e tests because the preprocessor
output channel is small (capacity of 16), hence it was filling up very
quickly and only a few uninteresting (i.e., irrelevant to the test
cases) records were lost.

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>
@antoninbas antoninbas added the kind/bug Categorizes issue or PR as related to a bug. label Feb 12, 2025
@antoninbas antoninbas added this to the Antrea v2.3 release milestone Feb 12, 2025
@antoninbas
Copy link
Contributor Author

/skip-all

@antoninbas antoninbas merged commit 3bf8441 into antrea-io:main Feb 12, 2025
59 of 61 checks passed
@antoninbas antoninbas deleted the use-correct-msg-channel-in-flowExportLoopProxy branch February 12, 2025 19:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants