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

golang: allow flushing buffer when processing the data asynchronously #37958

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

spacewander
Copy link
Contributor

Commit Message: golang: allow flushing buffer when processing the data asynchronously
Additional Description: This PR adds a feature that allows users to flush the data immediately when processing the data asynchronously.
Risk Level: Low
Testing: Integration test
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

Copy link

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #37958 was opened by spacewander.

see: more, trace.

@spacewander spacewander marked this pull request as ready for review January 10, 2025 11:52
@spacewander
Copy link
Contributor Author

The failure of CI is caused by low coverage of source/common/quic:

Per-extension coverage failed:
Code coverage for source/common/quic is lower than limit of 93.4 (93.3)

https://github.com/envoyproxy/envoy/actions/runs/12707270169

The CI on main branch also failed because of this:
https://github.com/envoyproxy/envoy/actions/runs/12696754958/job/35391513281

@phlax
Copy link
Member

phlax commented Jan 10, 2025

see #37959

@@ -90,6 +90,16 @@ updates:
interval: daily
time: "06:00"

- package-ecosystem: "gomod"
directory: "/contrib/golang/filters/http/test/test_data/buffer_flush"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@spacewander there is a current conversation about consolidating/rationalizing these deps to one

currently the go test deps all contain the same deps and whenever they change (ie protobuf) we get an avalanche of dependency updates (and ci)

any chance we could address this first? cc @doujiang24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants