Dev Container configuration file already exists but is not being used
@ryandanehy is already working on this.
Since Dec 16, 2023.
Assessment
This issue has not been assessed yet.
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.
- Dominant language
- C++
- Stars
- 85
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from ORNL/ReSolve
-
SystemSolver still uses string to select configuration optionsMay be free again A pull request for this issue was closed without being merged. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Support unpreconditioned GMRESMay be free again @kakeueda claimed this 47 days ago, and no pull request is open. Openenhancement iterative solver
Difficulty 3/5 1-2 days Newbie friendliness 55/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Support P and Q permutations provided by the user in `LinSolverDirectKLU`May be free again @stark256-spec claimed this 39 days ago, and no pull request is open. Openenhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
grizzlypeak3d/DJV#962 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day