Fix status conflict in exec publication #427
Merged
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
fufeck
force-pushed
the
fufeck_fix_status-conflict-in-exec-publication
branch
from
85f9e39 to
931ec28
Compare
fufeck
changed the title
MaGOs92
approved these changes
Feb 6, 2024
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.
Context
Lorsque le le JOB
sync_outdatedrun, les BALS qui étaientoutdatedmais dont lelastUploadedRevisionIdn'était pas la révision courante publiait normalement alors qu'elle devait normalement finir enConflicta cause d'une coquille dans la fusion du sync.Remplacement des
returnDocument: afterparnew: truecomme préconisé par la doc mongooseCela a surement entrainé des problème de conflit