Open inorick opened 2 years ago
Apparently, the issue was caused by running vscode as a snap package. Installing vscode as a native rpm solved the issue. This is odd as vscode runs unconfined, i.e. it was installed using the --classic
command line switch (https://snapcraft.io/docs/snap-confinement). This might be a snap issue.
I opened an upstream issue: https://github.com/microsoft/vscode/issues/139442
"command ... not found" is a weird error. You can try installing GitHub Issue Notebooks in the same environment, and use their github-issues.new
command, which basic does the same thing. If there is a similar error, it is most likely a vscode problem.
@njpipeorgan I am facing the same problem on my m1 mac.
@njpipeorgan I am facing the same problem on my m1 mac.
It does not seem to be a universal problem. You may try creating a .wlnb
file manually, and check whether you can use other functionalities of the extension normally.
It has been noted in #4 that the native m1 build of VS Code does not work with the extension because zeromq is not available.
I installed zeromq using homebrew (https://formulae.brew.sh/formula/zeromq), but the problem persists. And it seems it does support Apple silicon natively.
The "Manage Kernels" command doesn't work as well and displays the same error
Still having the same issue on both VS code/VS code insider snap on Ubuntu 20.04.4. On .deb it works, but fails to establish a connection to the server with the error message "Failed to find the kernel wolframscript in configurations. A kernel must contain a "command" field."
.
Still having the same issue on both VS code/VS code insider snap on Ubuntu 20.04.4. On .deb it works, but fails to establish a connection to the server with the error message
"Failed to find the kernel wolframscript in configurations. A kernel must contain a "command" field."
.
I fix this issue by rollback wolfram-language-notebook to 0.0.9. Not sure what changed causing the issue.
"command ... not found" is a weird error. You can try installing GitHub Issue Notebooks in the same environment, and use their
github-issues.new
command, which basic does the same thing. If there is a similar error, it is most likely a vscode problem.
@njpipeorgan The problem still exist on Ubuntu 22.04 with VSCode snap. I have tried GitHub Issue Notebooks
, it can create new file without problem.
I tried to create a new Wolfram Language notebook using the command provided by the extension. However, I encountered the following error. I am running Fedora Linux, if that matters.