VS Code Extension v1.12.0 does not create .tabby-client data directory on macOS Sonoma

[nicholasdehnen]

Describe the bug
I followed the quick start tutorial on the TabbyML website here. The server seems to work as I can access the WebUI, but the most recent VS Code extension v1.12.0 does absolutely nothing.

Clicking on "Connect to server.." gives: Command 'Tabby: Connect to Server...' resulted in an error - command 'tabby.setApiEndpoint' not found.

Looking at the log from the VS Code extension (see additional context), it attempts to access ~/.tabby-client/agent/data.json, which does not exist on my system:

❯ ls -la ~/.tabby-client
ls: /Users/user/.tabby-client: No such file or directory

I ended up reverting to the prior version 1.10.3 which shows the same error at first, but then seems to create the json file instead of breaking. I assume this functionality somehow broke in the transition from 1.10.3 to 1.12.0? After installing 1.10.3 and consequently updating to 1.12.0, the new version works as expected / outlined in the docs.

Information about your version

❯ tabby --version
tabby 0.18.0

❯ code --list-extensions --show-versions
charliermarsh.ruff@2024.50.0
eeyore.yapf@2024.9.126091437
ms-python.debugpy@2024.10.0
ms-python.python@2024.16.0
ms-python.vscode-pylance@2024.9.2
redhat.vscode-yaml@1.15.0
tabbyml.vscode-tabby@1.12.0
visualstudioexptteam.intellicode-api-usage-examples@0.2.8
visualstudioexptteam.vscodeintellicode@1.3.1

Information about your GPU
MacBook Air M2, running macOS Sonoma 14.6.1

Additional context
Tabby Extension v1.12.0 failing to start:

2024-10-04 11:58:54.856 [info] [Tabby] Activating Tabby extension...
2024-10-04 11:58:54.856 [info] [Tabby] Failed to create GitProvider, retry after 1000ms
2024-10-04 11:58:55.867 [info] [Tabby] Failed to create GitProvider, retry after 2000ms
2024-10-04 11:58:56.016 [info] (node:33554) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 newAttached listeners added to [hS]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `Code Helper (Plugin) --trace-warnings ...` to show where the warning was created)

2024-10-04 11:58:56.017 [info] node:internal/process/promises:391
    triggerUncaughtException(err, true /* fromPromise */);
    ^

[Error: ENOENT: no such file or directory, open '/Users/user/.tabby-client/agent/data.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/user/.tabby-client/agent/data.json'
}

Node.js v20.16.0

2024-10-04 11:58:56.027 [info] [Error - 11:58:56 AM] Server process exited with code 1.
2024-10-04 11:58:56.028 [info] [Error - 11:58:56 AM] Server initialization failed.
2024-10-04 11:58:56.028 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097 
2024-10-04 11:58:56.028 [info] [Info  - 11:58:56 AM] Connection to server got closed. Server will restart.
2024-10-04 11:58:56.028 [info] true
2024-10-04 11:58:56.029 [info] [Error - 11:58:56 AM] Tabby client: couldn't create connection to server.
2024-10-04 11:58:56.029 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097 
2024-10-04 11:58:56.173 [info] (node:33558) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 newAttached listeners added to [hS]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `Code Helper (Plugin) --trace-warnings ...` to show where the warning was created)

2024-10-04 11:58:56.174 [info] node:internal/process/promises:391
    triggerUncaughtException(err, true /* fromPromise */);
    ^

[Error: ENOENT: no such file or directory, open '/Users/user/.tabby-client/agent/data.json'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/Users/user/.tabby-client/agent/data.json'
}

---

Tabby Extension v1.10.3 by comparison:

2024-10-04 12:07:25.502 [info] [Tabby] Activating Tabby extension...
2024-10-04 12:07:25.502 [info] [Tabby] Failed to create GitProvider, retry after 1000ms
2024-10-04 12:07:26.401 [info] [Tabby] GitProvider created.
2024-10-04 12:07:26.553 [info] (node:33709) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 newAttached listeners added to [MR]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `Code Helper (Plugin) --trace-warnings ...` to show where the warning was created)

2024-10-04 12:07:26.565 [info] [Info  - 12:07:26 PM] [ConfigFile] Config file not exist, creating template config file.
2024-10-04 12:07:26.567 [info] [Info  - 12:07:26 PM] [TabbyAgent] Initializing...
2024-10-04 12:07:26.569 [info] [Error - 12:07:26 PM] [TabbyAgent] Failed to load stored data. {
  "error": {
    "errno": -2,
    "code": "ENOENT",
    "syscall": "open",
    "path": "/Users/user/.tabby-client/agent/data.json"
  }
}
2024-10-04 12:07:26.570 [info] [Info  - 12:07:26 PM] [TabbyAgent] Applying updated config...
2024-10-04 12:07:26.571 [info] [Debug - 12:07:26 PM] [CaCert] Loading extra certs from mac-ca.
2024-10-04 12:07:26.617 [info] [Debug - 12:07:26 PM] [CaCert] Loaded 104 extra certs.
2024-10-04 12:07:26.623 [info] [Info  - 12:07:26 PM] [proxy] Using proxy from environment variables.
2024-10-04 12:07:26.624 [info] [Debug - 12:07:26 PM] [TabbyAgent] Health check request: GET http://localhost:8080/v1/health. [95f09c31-f5e2-4cf3-b745-039151a3ee02]
2024-10-04 12:07:26.638 [info] (node:33709) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time.

2024-10-04 12:07:26.645 [info] [Debug - 12:07:26 PM] [TabbyAgent] Health check response status: 401. [95f09c31-f5e2-4cf3-b745-039151a3ee02]
2024-10-04 12:07:26.647 [info] [Info  - 12:07:26 PM] [TabbyAgent] Status changed: unauthorized.
2024-10-04 12:07:26.648 [info] [Info  - 12:07:26 PM] [TabbyAgent] Completed applying updated config.
2024-10-04 12:07:26.650 [info] [Info  - 12:07:26 PM] [TabbyAgent] Initialized.
2024-10-04 12:07:26.654 [info] [Tabby] Tabby extension activated.
2024-10-04 12:07:26.655 [info] [Info  - 12:07:26 PM] [CodeSearch] Created code search engine for recently changed files.

[wsxiaoys]

Thank you for reporting the issue. I can confirm that it can be reproduced. As a short-term workaround, please continue using version 0.17 (Tabby) / 1.10.3 (Tabby VSCode Extension).