Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Actual command not found, wanted to execute git.sync/11 #170117

Closed
SimonSiefke opened this issue Dec 27, 2022 · 10 comments
Closed

Actual command not found, wanted to execute git.sync/11 #170117

SimonSiefke opened this issue Dec 27, 2022 · 10 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) git GIT issues

Comments

@SimonSiefke
Copy link
Contributor

actual-command-not-found

Does this issue occur when all extensions are disabled?: Yes

  • VS Code Version: 1.74.2
  • OS Version: Ubuntu 22.10

Steps to Reproduce:

  1. Click on "git sync" button in the bottom left corner
  2. A notification is shown: "Actual command not found, wanted to execute git.sync/11"

The error only happens sometimes, which indicates that it might be a race condition (?)

Related issues:

@lszomoru
Copy link
Member

lszomoru commented Jan 2, 2023

@jrieken, any suggestions on how I should approach troubleshooting this issue? Thank you!

@lszomoru lszomoru added bug Issue identified by VS Code Team member as probable bug git GIT issues labels Jan 2, 2023
@jrieken
Copy link
Member

jrieken commented Jan 3, 2023

This is from a normal status bar item, right?

@lszomoru
Copy link
Member

lszomoru commented Jan 3, 2023

Yes, that is my understanding based on the issue description.

@jrieken
Copy link
Member

jrieken commented Jan 3, 2023

I believe @bpasero has a related/duplicate issues. This happens when the extension host already updated (and disposed a command) before the UI applied an update. Hence, the UI still refers to an old command that isn't available anymore

@VSCodeTriageBot VSCodeTriageBot added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 3, 2023
@VSCodeTriageBot
Copy link
Collaborator

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@VSCodeTriageBot VSCodeTriageBot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 3, 2023
@jrieken jrieken reopened this Jan 3, 2023
@bpasero
Copy link
Member

bpasero commented Jan 3, 2023

The one that is still waiting for a reproducible sample is: #165244

@lszomoru
Copy link
Member

lszomoru commented Jan 9, 2023

@SimonSiefke, it would be helpful if you would be able to provide a repro so that we can get to the bottom of this. Thanks!

@bpasero
Copy link
Member

bpasero commented Jan 10, 2023

Jo pushed a fix for #165244, so it should be fine now.

@lszomoru
Copy link
Member

Thanks @bpasero. Closing this as duplicate of #165244.

@wjandrea
Copy link

wjandrea commented Feb 7, 2023

FWIW, I was experiencing a similar issue and jrieken's comment pointed me in the right direction. I just ran Developer: Reload Window (workbench.action.reloadWindow) and it was fine.

@github-actions github-actions bot locked and limited conversation to collaborators Feb 24, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug *duplicate Issue identified as a duplicate of another issue(s) git GIT issues
Projects
None yet
Development

No branches or pull requests

6 participants