Open repository keeps reusing broken local copy even after update is pushed

[mjbvz]

Testing #2407

Repo

1. Using a repository with a container that has a initializeCommand that will fail (https://github.com/mjbvz/test-contianer/tree/715ae930cc472905d837c12c7548c23b550a8633)
2. Try opening this repo using the Open Repository command
3. It fails as expected
4. Now push an update the repository that fixes the issue
5. Run Open repository again and select the same location

Bug
VS Code still uses the old container definition. I can't figure out how to force it to update to the new repository definition.

I see the following logs:

[904 ms] fatal: destination path '/workspaces/test-contianer' already exists and is not an empty directory.
[929 ms] Repository 'mjbvz/test-contianer.git' was already cloned into '/workspaces/test-contianer'.

Related

• Container: stuck with init command yarn #2428

[chrmarti]

Could be solved with #2428 (comment).

[chrmarti]

The error dialog now offers to open a 'Recovery Container' in which the Git repo can be advanced to the latest commit.