fix: Possible race condition on Orchestrator API initialization #9713
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
ovr
commented
Jun 25, 2025
|
|
||
| // orchestrator options can be empty, if user didn't define it. | ||
| // so we are adding default and configuring queues concurrency. | ||
| const orchestratorOptions = |
There was a problem hiding this comment.
As you can see, there is an await point here at (await this.orchestratorOptions(context)) || {},. it's defined between first get/set and set as init point.
With this, it's possible to have two orchestrator API instances, if it's called immediately at one time.
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.
No description provided.