-
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
[BEAM-11167] Updates dill package to version 0.3.5.1 #17669
Conversation
Can one of the admins verify this patch? |
4 similar comments
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Can one of the admins verify this patch? |
Run Postcommit 3.8 |
Run Python 3.8 PostCommit |
R: @tvalentyn @y1chi |
Run Python 3.8 PostCommit |
Codecov Report
@@ Coverage Diff @@
## master #17669 +/- ##
==========================================
- Coverage 74.09% 74.06% -0.03%
==========================================
Files 697 697
Lines 91980 91980
==========================================
- Hits 68148 68129 -19
- Misses 22583 22602 +19
Partials 1249 1249
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
Looks like the tool that pulls licences is having trouble to get dill's license now:
|
@@ -17,7 +17,7 @@ | |||
# Run ./gradlew :sdks:python:container:generatePythonRequirementsAll to update. | |||
# Do not edit manually, adjust ../base_image_requirements_manual.txt or | |||
# Apache Beam's setup.py instead, and regenerate the list. | |||
# You will need Python intepreters for all versions supported by Beam, see: | |||
# You will need Python interpreters for all versions supported by Beam, see: |
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.
you'd have to fix this in the generator script
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.
Done.
@tvalentyn do you think this needs a note in changes.md since this upgrade hasn't happened in 3 years? Or do you think library version upgrades is such a common event it's not worth noting? |
It's worth noting the implications. Dill is an implementation detail that users don't care about. But there is a risk that some pipeline would fail to launch because something suddenly fails to pickle after upgrading to a new SDK. I am not very worried about 0.3.4, as it's been around for a while. But 0.3.5 (which may happen sometime soon), might include rough edges due to uqfoundation/dill#443. |
OK, I made a note in change.md. It doesn't go into details or implications deeply. Is this adequate? |
Let's come back to this when the 2.38.0 release is finalized. |
Co-authored-by: tvalentyn <tvalentyn@users.noreply.github.com>
I guess I don't understand why we should come back to this waiting on a release finalization. Isn't the release already cut at a give PR, and future PR's (like this one) shouldn't effect the release? |
It's just for the benefit of managing the release activities we do internally - it's going to be a little easier if we wrap up the release before making this change, so if this is not too urgent, I'd wait ~1 week or so. |
Run PythonDocker PreCommit |
Run Portable_Python PreCommit |
We can proceed with merging this now. Can you address conflicts & test failures? |
Run Portable_Python PreCommit |
Co-authored-by: tvalentyn <tvalentyn@users.noreply.github.com>
Run Python 3.8 PostCommit |
Dill hasn't been upgraded in 3 years. We need to keep the dependency tight. Because dill doesn't have backwards compatibility between minor versions workers and runners MUST be on the same minor version (in this case 0.3.5.1).
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:
R: @username
).[BEAM-XXX] Fixes bug in ApproximateQuantiles
, where you replaceBEAM-XXX
with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.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.