[BUG]: Command Palette not recognizing 'freeCodeCamp: Run Course'

[Dors-Coding-School]

Issue/Experience

I did all the instructions you mentioned to set up my environment for Web3, but it was not displaying on the command palette "freeCodeCamp: Run Course".

I was able to fix it by downloading the extension of 'freeCodeCamp - Courses' in my VS Code. It would be nice if you mention this hint if people get stuck like I was.

[ShaunSHamilton]

Hello there,

This should not happen. When opening bug reports, please follow the given template to provide the necessary details:

Output of running node tooling/camper-info.js from the workspace root

[moT01]

That extension is one of the last things added to the container. It can look like everything is finished, but it may still be installing that - so the command doesn't always show up right away. If you wait a second, it should finish installing and be there.

Although, that doesn't really sound like what happened here since you manually installed the extension. Probably would have seen that the installation was in progress.

[duartenunes86]

It's not working

[ShaunSHamilton]

@duartenunes86 I suggest opening a new issue for your issue, as it does not look the same.

Your workspace does not look correct - the container should not contain a web3-curriculum in the workdir, it should have web3-curriculum/ as the workdir. Also, the "Docker in Docker" bit does not look correct - where is that coming from?

[duartenunes86]

Here is the web3-curriculum in the image.....when I was setting up the things asked me if I wanted alpine, docker, etc

[DevChaudhary78]

Heya everyone, I am just curios, is anyone able to find any solution for this?

I am unable to run the project as it is not showing freeCodeCamp: Run Course

[ShaunSHamilton]

@DevChaudhary78 I am still unable to reproduce any issue here. So, if you can provide any more information (dev container build logs, or similar), then that might help debugging.

[DevChaudhary78]

Hello and Good Afternoon @ShaunSHamilton, thanks for responding quickly, and sorry for the delay from my end.

I've pasted my logs on https://ctxt.io/2/AADIvF0qFg, though there isn't anything that might help according to me as it successfully builds everything.

The only weird thing I found when opening the code in vscode using code . in the web3-curriculum directory, is that it is not showing any files in the vscode explorer, and funny enough I can see all the files in the terminal.

One more thing which I should mention and might be helpful is that whenever I run Dev Containers: Rebuild and Reopen in Container, it asks me these questions shown below in the image.

PS: I am using WSL2 with Ubuntu on Windows 10

I hope I've provided a good understanding of the situation, if not please feel free to ask follow-up questions.

Thanks and appreciate your efforts, and have a good day (:

[ShaunSHamilton]

it is not showing any files in the vscode explorer

This is expected, because we have a .vscode/settings.json config to hide "unnecessary" files for the duration of the course.

whenever I run Dev Containers: Rebuild and Reopen in Container, it asks me these questions shown below in the image.

This is annoying, and is a bug with the Dev Containers extension that pops up every now and again: freeCodeCamp/solana-curriculum#126

If you can try downgrading the extension until it works?

---

As for the logs, they do not look complete. Perhaps fixing the dev containers extension issue will resolve this. Otherwise, a rebuild without cache might help.

Sorry for the annoyances.

[DevChaudhary78]

Hello @ShaunSHamilton, thanks for your response.

If you can try downgrading the extension until it works?

Is there any specific version, which can help? I've tried the last 4 versions, and nothing seems to be working.

Thanks

[ShaunSHamilton]

@DevChaudhary78 Sorry. My message was not very helpful. Try downgrading to 0.309.0:

freeCodeCamp/near-curriculum#57 (comment)

[mena234]

Same issue here.

[DevChaudhary78]

No worries @ShaunSHamilton, thanks a lot for all your help, it finally worked for me. So the culprit was the dev containers plugin all along, and downgrading it to 0.309.0 worked for me.

Have a great day.

[mena234]

@ShaunSHamilton
I got this error when I downgraded to 0.309.0 and then run Dev Containers: Rebuild and Reopen in Container