KEMBAR78
fix: Make EOS Matching more robust by emkornfield · Pull Request #1128 · googleapis/java-bigquerystorage · GitHub
Skip to content

Conversation

@emkornfield
Copy link
Contributor

@emkornfield emkornfield commented Jun 11, 2021

fix: Make EOS Matching more robust

Clients are seeing a different variant now: Received unexpected EOS on empty DATA frame from server

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

  • Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
  • Ensure the tests and linter pass
  • Code coverage does not decrease (if any source code was changed)
  • Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕️

fix: Make EOS Matching more robust

Clients are seeing a different variant now: Received unexpected EOS on empty DATA frame from server
@emkornfield emkornfield requested review from a team and shollyman June 11, 2021 15:41
@snippet-bot
Copy link

snippet-bot bot commented Jun 11, 2021

No region tags are edited in this PR.

This comment is generated by snippet-bot.
If you find problems with this result, please file an issue at:
https://github.com/googleapis/repo-automation-bots/issues.
To update this comment, add snippet-bot:force-run label or use the checkbox below:

  • Refresh this comment

@product-auto-label product-auto-label bot added the api: bigquerystorage Issues related to the googleapis/java-bigquerystorage API. label Jun 11, 2021
@google-cla google-cla bot added the cla: yes This human has signed the Contributor License Agreement. label Jun 11, 2021
emkornfield referenced this pull request in grpc/grpc-java Jun 11, 2021
Empty DATA frames with EOS tell a stronger tale as to where the server
may have its bug.
@emkornfield
Copy link
Contributor Author

It looks like grpc/grpc-java@60d3e7c broke the logic

@emkornfield
Copy link
Contributor Author

@stephaniewang526 would you mind taking a look.

@emkornfield
Copy link
Contributor Author

Integration test failure looks related to the write functionality

@shollyman shollyman added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 11, 2021
@shollyman
Copy link
Contributor

re-running to get around the loadshed failure

@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 11, 2021
@shollyman shollyman added automerge Merge the pull request once unit tests and other checks pass. kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Jun 11, 2021
@shollyman
Copy link
Contributor

Still getting loadshedding responses from the write backend

@shollyman shollyman added kokoro:force-run Add this label to force Kokoro to re-run the tests. and removed kokoro:force-run Add this label to force Kokoro to re-run the tests. labels Jun 11, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Jun 11, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit 3b5cdbe into googleapis:master Jun 11, 2021
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge Merge the pull request once unit tests and other checks pass. label Jun 11, 2021
shubhwip pushed a commit to shubhwip/java-bigquerystorage that referenced this pull request Oct 7, 2023
🤖 I have created a release *beep* *boop*
---


### Updating meta-information for bleeding-edge SNAPSHOT release.

---
This PR was generated with [Release Please](https://togithub.com/googleapis/release-please). See [documentation](https://togithub.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

api: bigquerystorage Issues related to the googleapis/java-bigquerystorage API. cla: yes This human has signed the Contributor License Agreement.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants