[ENG-6427] Added measures to secure executing of embargoes #10983
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
|
Researched the issue, was not able to reproduce locally any case, as no workflows provided to get registration to that condition. Found only one case when potentially this can occur due to Node and Embargo inconsistent (failing to set privacy, but embargo is completed) |
bodintsov
changed the title
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.
Purpose
Fix issue when registrations do not become public when embargo engs
Changes
TBD
QA Notes
TBD
Documentation
TBD
Side Effects
TBD
Ticket
(https://openscience.atlassian.net/browse/ENG-6427)