When more than one instance of the same PipelineOption subclass is detected, use the first one. #36704
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When more than one instance of the same PipelineOption subclass is detected, use the first one instead of the last one.
This change helps to avoid a race condition where CloudPickle sometimes creates [skeleton classes] (https://github.com/apache/beam/blob/735864d4d5cd0abda9b1181c6459eb877218c16a/sdks/python/apache_beam/internal/cloudpickle/cloudpickle.py#L646C1-L647C1) and leaves then uninitiazlied, and eventually garbage collected. This happens when an initialized skeleton already exists for a given
class_tracker_id. An uninitialized skeleton doesn't have an overloadedPipelineOptionSubclass._add_argparse_argsbound method, and hence may cause difficult to debug error where pipeline options may not be properly parsed.Picking the first subclass empirically reduces the risk of picking the 'wrong' subclass, but a better fix would be to avoid creating uninitialized skeletons when they are not necessary to reduce sideeffects of unpickling.
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.mdwith 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.