NCADynamicQuantitiesExt is missing after I installed Pumas 2.7

Installation
21

{

"julia.executablePath": "julia.exe +Pumas@2.7.0",

"julia.environmentPath": "C:\\\\Users\\\\Abhiram\\\\.julia\\\\environments\\\\Pumas@2.7.0",

"window.commandCenter": false,

"terminal.integrated.commandsToSkipShell": \[

    "language-julia.interrupt"

\],

"julia.symbolCacheDownload": true,

"julia.enableTelemetry": true,

"julia.persistentSession.alwaysCopy": true,

"workbench.editor.empty.hint": "hidden",

"workbench.editorAssociations": {

    "\*.xlsx": "default"

},

"terminal.integrated.profiles.windows": {

    "PowerShell": {

        "path": "C:\\\\Windows\\\\System32\\\\WindowsPowerShell\\\\v1.0\\\\powershell.exe"

    },

    "Command Prompt": {

        "path": \[

            "${env:windir}\\\\Sysnative\\\\cmd.exe",

            "${env:windir}\\\\System32\\\\cmd.exe"

        \],

        "args": \[\],

        "icon": "terminal-cmd"

    },

    "Git Bash": {

        "source": "Git Bash",

        "icon": "terminal-git-bash"

    }

},

"terminal.integrated.defaultProfile.windows": "PowerShell"

}
@Michael PFA

22

I’m getting the same error again and again
Ive tried uninstall and reinstall
can we join over a call if the query is not resolved?

23

Resolved on a call. Same issue as faced in other threads where the juliaup channel was not correctly honored by the vscode julia extension. Resolved by going into a terminal and running juliaup default 1.11.5~x64. Note that the choice of default depends on the version of Pumas that you’d like to use as default. For Pumas@2.7.0 it is 1.11.5~x64, while for Pumas@2.7.1 it is 1.11.7~x64. Run juliaup st and read the printed table to see which channel should be set as default.