Error running netconf.connect.

[MarkAtAgilliance]

Using VS Code on Win 11 pro
Netconf Extension version 2.0

Connection properties are

   "netconf.serverList": [

        {
            "id": "IHUB-831",
            "host": "10.253.0.2",
            "port": 831,
            "username": "admin",
            "password": "<<Hidden>>",
            "clientCapabilities": [
                "urn:ietf:params:netconf:base:1.0",
                "urn:ietf:params:netconf:base:1.1"
            ]
        }
    ],
    "netconf.sshDebug": true

Debug console shows:

notificationsAlerts.ts:42
Error running command netconf.connect: Cannot read properties of undefined (reading 'logger'). This is likely caused by the extension that contributes netconf.connect.

[MarkAtAgilliance]

ok, this may only happen when user and workplace settings are adjusted. I am trying to narrow it down and will update. I jus cleared all the workspace settings and it appears to be connecting again.

Ok, some testing.

1. When I click the "Ssh Debug" on the user settings tab, then the failure occurs.
2. When I unclick the Debug SSH, the failure remains.
3. If I go into "Workspace" tab and click "edit in settings.json" then remove everything and save, then the failure is removed and the connection occurs.

It also appears that if anything is in the workplace settings file, (even the blank "serverList" array) then problems occur.

Right now my overall problem is that I cannot debug SSH problems I am having because the connection with any form of debug setting is not working.

[wisotzky]

Thanks @MarkAtAgilliance

I've pushed quite some updates. I've seen the issue around SSH Debug. It should be fixed now. Please use the side bar as primary source for add/update/delete managed device. With the latest version you are able to cross-navigate to JSON settings. I anticipate to use "User Settings" and "Remote Settings". Indeed, Workspace settings are taking preference and should be removed. Remind, Workspace settings are no longer required since vscode-netconf now support multiple parallel connections.

Let me know if there are any rather findings.

Thx!!!

[MarkAtAgilliance]

Thanks - will check out on Monday.

[wisotzky]

@MarkAtAgilliance, could you confirm the issue is resolved with latest release?
Would like to close this issue.