Why gcc?

Why the installation of Node when you're doing that below via nvm?

The gcc is here because on the shell script that runs after creation of the docker container, I am installing requirements for users of the dev container to be able to run our tests, and for "build/smoke-test-requirements.txt", specifically, throws " No such file or directory: 'gcc' " if I do not include/download gcc on the docker file.

Good point! I've thought nvm only took take of managing and usage of specific version of node and npm, but realized nvm not only take cares of the controlling of the version, but also the installation itself.

Specifically the the build for psutil (seems to be a Python library that has to do with system utils and processes), more specifically "build/temp.linux-aarch64-cpython-37/psutil" is failing with " is failing with the message "ERROR: Failed building wheel for psutil" and "command 'gcc' failed: No such file or directory: 'gcc'"

I think this is unique to your machine, since https://pypi.org/project/psutil/#files has wheel files for x64 and i686 for Linux, just not ARM.

But specifically, which dependency is pulling it in? Looking at https://github.com/microsoft/vscode-python/blob/main/build/smoke-test-requirements.txt there is no direct dependency on it. I also don't know why any of that is being installed since we have no kernel support, so I suspect the entire file can be dropped since we don't ship Jupyter in-box anymore and the middleware issue I believe has been fixed. Karthik Nadig (@karthiknadig) do we still need these installed?

Partially. We still have the old installer that installs pandas, jupyter etc. But, I don't think it requires these installed for testing. I don't see direct references to these packages in our test code. We might want to verify this by removing each package in the list, and running the tests to confirm.

I think this is unique to your machine, since https://pypi.org/project/psutil/#files has wheel files for x64 and i686 for Linux, just not ARM.

After testing out installing smoke-test build requirement on both Codespaces directly, and via VS Code dev container extension, I found that the gcc is only needed to be installed for ARM host(?) machine.

I found this quite weird, because I would assume the platform is Fedora linux as I am accessing the dev container through the VS Code dev container extension.. the build for smoke-test-requirement is SUCCESSFUL when accessed via Codespaces, but fails when the dev container is accessed via VS Code dev container extension on my ARM machine.

Should I leave the gcc installation included?

Partially. We still have the old installer that installs pandas, jupyter etc. But, I don't think it requires these installed for testing. I don't see direct references to these packages in our test code. We might want to verify this by removing each package in the list, and running the tests to confirm.

When you say running the "tests", do you mean only the smoke test, or all the other tests too, including like unit tests and functional tests?