Reorder back-end plugin deployment to prevent early promise resolution #13643
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.
What it does
Upon startup, we the front end indirectly waits for the initial deployment of plugins before loading their contributions. Because of parallel execution of back end/headless deployment, the corresponding promise was resolved too early and the list of plugins was incomplete.
Workaround for #13638
Contributed on behalf of STMicroelectronics
How to test
Repeat the "how to reproduce" from the linked issue. The installed plugins should show up reliably in the UI.
Follow-ups
#13641
#13642
Review checklist
Reminder for reviewers