Register test commands before first await to prevent activation race condition #25654
+93
−71
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.
fixes #22783 and #21865
The
python.configureTestscommand was registered after multiple async operations during extension activation, creating a race condition where users could invoke the command before it was registered.Changes
Extract command registration: Created standalone
registerTestCommands()function intesting/main.tscontaining all test command handlers (Tests_Configure,Tests_CopilotSetup,CopyTestId)Register synchronously before first await: Moved
unitTestsRegisterTypes()andregisterTestCommands()toextension.tsimmediately afterinitializeStandard(), beforeexperimentService.activate()Remove duplicate registrations: Cleaned up original registration in
UnitTestManagementService.activate()andactivateLegacy()