Dev Container configuration file already exists but is not being used
Open
@ryandanehy is already working on this.
Since Dec 16, 2023.
bug
documentation
- Dominant language
- C++
- Stars
- 84
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Following the instructions on how to set up a dev container to develop ReSolve documentation, I ran out into an issue where vscode pops up a dialog box saying that json configuration file already exists for the dev container, but refuses to use it (there are 2 options none of which will run existing configuration). This issue seems to be a documented bug in vscode.
The workaround that get me pass this point was to add line like this
"initializeCommand": "ls"
at the end of devcontainer.json file. I don't know how and why, but it worked :P.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.