-
Notifications
You must be signed in to change notification settings - Fork 748
[GOBBLIN-1972] Fix CopyDataPublisher to avoid committing post-publish WUs before they've actually run
#3844
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
Merged
Will-Lo
merged 2 commits into
apache:master
from
phet:fix-copy-data-publisher-post-publish-commit
Dec 7, 2023
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
Maybe not for this PR, but if this stems from multiple categories of workloads being misidentified maybe we should have this as its own separate class and have a stronger type system around workunit collections?
Uh oh!
There was an error while loading. Please reload this page.
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.
I don't see mis-identification as the underlying reason for the regression. rather it was more likely not appreciating how presumptuous
WorkUnitState::getWorkingState()is about the WU it's invoked on having already executed. I doubt it was clear (certainly it shocked me!) that it would fall back on the enclosing job's state to provide state for a WU that had itself never run!as for the
WorkUnitStatesHelper, I don't presently foresee utility beyondCopyDataPublisher. if the opportunity for leverage arises later, we can change fromprivateand/or unnest it at that point.