Closed ghost closed 2 years ago
I have similar problem with you, and I haven't found a solution yet.
Thanks for your feedback. It is caused by a bug in the extension. As a workaround, try restart VS Code or reload the VS Code window after changing the kernel configuration.
Thanks for your feedback. It is caused by a bug in the extension. As a workaround, try restart VS Code or reload the VS Code window after changing the kernel configuration.
I tried your solution and now a new error appears: The kernel has stopped due to the following error: Failed to create a ZeroMQ local server on port 55340.
I managed to get it to work by simply restarting the computer. There were so many kernels open in the background, check with Activity Monitor for "wolfram" processes active.
There's a an already closed issue that solves this problem. Check it out.
Hello everyone, this seems to be an intermittent problem, what works for me is:
When I first start VSCode I get the error described above, what I do is:
View Terminal -> Select: Output -> Select: Wolfram Language Notebook.
Run a very Simple Line: In 1>: 4 + 1
Then, in my case, VSCode asks me to choose an engine, I choose the first one on the list, it does is thing, and it works.
So far this is the most successful procedure I got.
When trying to run the notebook it says "The kernel has stopped due to the following error: The first packet is not a InputNamePacket; packet=$Failed". How should I fix this?
It's a fresh install of everything.