-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[cherry-pick] Catch EOFError along with StopIteration (#28896) #28901
Conversation
* catch EOF instead of StopIteration * add stop iteration to close * catch both stop iteration and EOF
Run Python 3.8 PostCommit |
R: @kennknowles |
Codecov Report
@@ Coverage Diff @@
## release-2.51.0 #28901 +/- ##
==================================================
- Coverage 72.25% 72.21% -0.04%
==================================================
Files 684 684
Lines 101070 101070
==================================================
- Hits 73024 72992 -32
- Misses 26467 26499 +32
Partials 1579 1579
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 10 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Assigning reviewers. If you would like to opt out of this review, comment R: @robertwb added as fallback since no labels match configuration Available commands:
The PR bot will only process comments in the main thread (not review comments). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please go add tests!
This is caught only in postcommit, right? There is no additional unit test added for this. It should have unit tests to catch it earlier. |
yes. I checked bigquery_test.py and there are no tests for |
Stopping reviewer notifications for this pull request: review requested by someone other than the bot, ceding control |
|
CC: @jrmccluskey |
In the Python PostCommit? That should have gotten fixed... @tvalentyn ? Stems from removing tensorflow from base python containers |
Closing this PR in favor of adding a note to known issues of upgrading fastavro to 1.8.4. Anyway, the tensorflow module not found error is coming out of example file involved in a test. There is one more vertex_ai test that runs fine. So I don't think there is a problem with the model handler itself and we can ignore that failing test to unblock from releasing and handle on master branch. WDYT @jrmccluskey |
Fixes the fastavro regression with 1.8.4 release causing failures for Python PostCommits
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
addresses #123
), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, commentfixes #<ISSUE NUMBER>
instead.CHANGES.md
with noteworthy changes.See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)
See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.