njpipeorgan / wolfram-language-notebook

Notebook support for Wolfram Language in VS Code
Apache License 2.0
159 stars 11 forks source link

Failed to find the kernel wolframscript in configurations. A kernel must contain a "command" field. #26

Open giammi56 opened 2 years ago

giammi56 commented 2 years ago

On the deb version of VS code, the kernel cannot run because the "command" is not found, although it is in the .json file.

image

Version: 1.67.2 Commit: c3511e6c69bb39013c4a4b7b9566ec1ca73fc4d5 Date: 2022-05-17T18:23:40.286Z Electron: 17.4.1 Chromium: 98.0.4758.141 Node.js: 16.13.0 V8: 9.8.177.13-electron.0 OS: Linux x64 5.13.0-44-generic

settings.json

{
    "editor.bracketPairColorization.enabled": true,
    "editor.guides.bracketPairs":"active",
    "jupyter.alwaysTrustNotebooks": true,
    "python.languageServer": "Pylance",
    "jupyter.askForKernelRestart": false,
    "explorer.confirmDelete": false,
    "files.trimTrailingWhitespace": true,
    "jupyter.interactiveWindowMode": "perFile",
    "explorer.confirmDragAndDrop": false,
    "workbench.editorAssociations": {
        "*.out": "hexEditor.hexedit",
        "*.ipynb": "jupyter-notebook"
    },
    // "jupyter.maxOutputSize": 1200,
    "diffEditor.codeLens": true,
    "C_Cpp.updateChannel": "Insiders",
    "r.rterm.linux": "/home/userme/.local/bin/radian",
    "r.bracketedPaste": true,
    "r.lsp.debug": true,
    "notebook.cellToolbarLocation": {
        "default": "right",
        "jupyter-notebook": "left"
    },
    "window.zoomLevel": -1,
    "explorer.sortOrder": "type",
    "debug.javascript.autoAttachFilter": "always",
    "wolframLanguageNotebook.kernel.configurations": {

        "wolframscript": {
            "type": "local",
            "command": "wolframscript",
            "ports": "49152-65535"
        }
    }
}
njpipeorgan commented 2 years ago

The configuration file looks okay. The error message is a bit misleading, since it can be the case that the extension did not find wolframLanguageNotebook.kernel.configurations at all, e.g. when this entry is in the Workspace settings (instead of User settings). I suggest that you may remove kernel configurations from all the settings, add the kernel from the prompt by the extension and see if it works.