You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Configure test command is not registered when the extension activates #21865
Daniel Imms (@Tyriar) do you remember what your setup looked like when you got this notification? Was the python extension activated yet? Had you ever run / configured tests in this workspace before?
Eleanor Boyd (@eleanorjboyd) I'm pretty sure it was happening because the python extension wasn't activated, meaning python.configureTests was not working properly as an activation event.
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
The user should never be able to see a message about a command missing. I think the right thing here is that all commands should be registered upon activation, otherwise there's a chance of this happening.
Activity
eleanorjboyd commentedon Aug 29, 2023
Daniel Imms (@Tyriar) do you remember what your setup looked like when you got this notification? Was the python extension activated yet? Had you ever run / configured tests in this workspace before?
Tyriar commentedon Aug 29, 2023
Eleanor Boyd (@eleanorjboyd) I'm pretty sure it was happening because the python extension wasn't activated, meaning python.configureTests was not working properly as an activation event.
eleanorjboyd commentedon Oct 4, 2023
To follow up on this, would the desired outcome just be for the action to not show in the command palette until the extension has activated?
brettcannon commentedon Nov 30, 2023
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.
Tyriar commentedon Nov 30, 2023
The user should never be able to see a message about a command missing. I think the right thing here is that all commands should be registered upon activation, otherwise there's a chance of this happening.
5 remaining items
eleanorjboyd commentedon Dec 15, 2023
closing as we cannot get a consistent repro, please reopen if this changes. Thanks!
Tyriar commentedon Dec 15, 2023
My guess is this happens because you activate the commands after you have awaited at least once in the activate command:
vscode-python/src/client/activation/activationManager.ts
Line 100 in db6e15e
If so, the fix would be either:
Register test commands before first await to prevent activation race …
eleanorjboyd commentedon Dec 18, 2025
fixed by dc7f9bf
eleanorjboyd commentedon Jan 5, 2026
dup of #22783, no need to verify