Repository navigation
docs: fix workflow start duplicate policy in every locale - #358
Merged
Merged
Conversation
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Correction
Refs #357. Close after deployment is verified.
The documented start request used
duplicate_policy: "reject", which the Server rejects with HTTP 422. Use canonicalfailand document both accepted policies, the omitted/null default and active versus closed-run outcomes. No policy reopens a closed run.English and all seven translations are updated together, including each reviewed source hash. The validator, WorkflowStartService mapping and Core duplicate-start decision were read directly. No runtime/API change is needed.
Focused translation checks pass: all seven locales have 105 current guides with reviewed source hashes, and their executable code blocks match English. No source-hash bypass or English fallback was added.
Actual isolated published Server 2.11.0, index b29157eb2cf844916debbbb3c01b3257672e0dece778a9c6fa539043a3038f02, passes the literal request read from this page: HTTP 201. Ten business HTTP controls cover invalid
reject/422, explicitfail, duplicate failure, omitted/null defaults, activeuse-existing/same run, closure, refusal of both policies after closure and a new id. The first recorder correctly observed HTTP 201 but then expected an absentstartedresponse key; that fixture attempt remains unsuccessful. A fresh database and a recorder using the canonicaloutcomefield pass all controls. No runtime, source or deadline was changed.The published image's WorkflowController 45014ec5 and WorkflowStartService 6a733644 hashes exactly match current published Server 2.11.1 source 5336a98d. This is a 2.11.0 HTTP acceptance with unchanged start implementation, not a claim that the 2.11.1 image was installed. The API stopped with exit 0 and no OOM. All runtime, database and network scratch is retired. No production request or new image pull. Normal source checks and live-site deployment remain pending.