EVA-2751 - move update of executionContext to fix resume in accessioning pipeline #331
Conversation
This file contains 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
apriltuesday
changed the title
|
As this isn't needed for the Python resumption in EVA-2404, I'm moving this to the other ticket. |
sundarvenkata-EBI
approved these changes
Feb 11, 2022
tcezard
approved these changes
Feb 14, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I can't find anywhere where it says you can't update the
executionContextin theopenmethod, but it does seem to be recommended to do so inupdateinstead... and empirically, when I ran in dev, the context is only persisted correctly to the job tracker when I make this change.