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

Use response buffer to address stream request issue #679

Merged
merged 2 commits into from
Feb 15, 2025

Conversation

Jeffwan
Copy link
Collaborator

@Jeffwan Jeffwan commented Feb 14, 2025

Pull Request Description

  1. Even in buffer mode, single request has several chunks. Our code doesn't address this issue in the past.
  2. Increase the buffer limit
  3. Use a response buffer to handle the multiple chunks just in case.

After this change, the e2e flaky issue should be gone

Related Issues

Resolves: #675

Important: Before submitting, please complete the description above and review the checklist below.


Contribution Guidelines (Expand for Details)

We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

  • [Bug]: Corrections to existing functionality
  • [CI]: Changes to build process or CI pipeline
  • [Docs]: Updates or additions to documentation
  • [API]: Modifications to aibrix's API or interface
  • [CLI]: Changes or additions to the Command Line Interface
  • [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

  • PR title includes appropriate prefix(es)
  • Changes are clearly explained in the PR description
  • New and existing tests pass successfully
  • Code adheres to project style and best practices
  • Documentation updated to reflect changes (if applicable)
  • Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

ResponseBody.EndOfStream sometimes is false even we use buffered mode. Current implementation does not take this into the consideration.

Signed-off-by: Jiaxin Shan <[email protected]>
@Jeffwan Jeffwan force-pushed the jiaxin/unexpected-eof branch from c50369c to 6ddf774 Compare February 15, 2025 00:00
@Jeffwan
Copy link
Collaborator Author

Jeffwan commented Feb 15, 2025

As we have to cut v0.2.0 release this weekend, I will merge this one and we can review this changes next week

@Jeffwan Jeffwan merged commit f3abcc8 into main Feb 15, 2025
10 checks passed
@Jeffwan Jeffwan deleted the jiaxin/unexpected-eof branch February 15, 2025 05:56
gangmuk pushed a commit that referenced this pull request Feb 19, 2025
* Increase the connection bufferLimit to avoid end_of_stream=false case

ResponseBody.EndOfStream sometimes is false even we use buffered mode. Current implementation does not take this into the consideration.

Signed-off-by: Jiaxin Shan <[email protected]>

* Use a response buffer to resolve the end_of_stream issue

Signed-off-by: Jiaxin Shan <[email protected]>

---------

Signed-off-by: Jiaxin Shan <[email protected]>
varungup90 pushed a commit that referenced this pull request Feb 20, 2025
* Increase the connection bufferLimit to avoid end_of_stream=false case

ResponseBody.EndOfStream sometimes is false even we use buffered mode. Current implementation does not take this into the consideration.

Signed-off-by: Jiaxin Shan <[email protected]>

* Use a response buffer to resolve the end_of_stream issue

Signed-off-by: Jiaxin Shan <[email protected]>

---------

Signed-off-by: Jiaxin Shan <[email protected]>
Signed-off-by: Varun Gupta <[email protected]>
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.

error reading response body: unexpected EOF investigation
1 participant