wakatime-ls not starting for Python files

[iwinux]

Problem

zed-wakatime works as an LSP in Zed and it only starts when a file is opened. It has been working fine until last week. Some unknown updates seem to have broken this mechanism for Python files recently.

Reproduce

1. start a fresh instance of Zed
2. open a Python file
3. check LSP status - only ruff & basedpyright are started
4. open another non-Python file
5. check LSP status again - wakatime-ls is started
6. close the non-Python file - wakatime-ls will be stopped after a while

Env

• Zed 0.205.6
• wakatime-ls-v0.1.9
• wakatime-cli-v1.131.0

[fmleo]

I could reproduce the problem as described above

I haven't done any extensive testing but it seems like a temporary fix could be simply adding "wakatime": {} (empty config for the LSP) to the "lsp" key in settings.json if you use .wakatime.cfg.

[mollyvita]

can confirm this, still happens on v0.209.0 95780e setting the key in settings.json or setting the key in .wakatime.cfg and adding the empty json key both don't work not sure whether i can test something else here

[bestgopher]

Could you provide a minimal repository that I can clone to reproduce the issue?

[mollyvita]

while trying things out, i had a realization: could this possibly be caused by windows? after some testing, wakatime download now just gets stuck for whatever reason. i tried setting the api key in settings.json and putting it in the cfg file as usual https://files.catbox.moe/24jdru.mp4 i can still make a repo real quick, i doubt that it would change much in case there are any logs i can drop, will do

[mollyvita]

testing more with wakatime-cli installed gives me some interesting results LSP logs if I set the API key in .wakatime.cfg:

setting the API key in Zed's settings gives pretty normal output (only Send: headers are shown in logs for whatever reason), but it doesn't look like it changes anything in wakatime

here's another recording with the python issue, but now i feel like wakatime just doesn't work for me :( https://files.catbox.moe/dl3odc.mp4 the recording shows that LSP logs actually detect some changes on JSON file (settings.json), but the second i go to a Python file it just stops

[bestgopher]

while trying things out, i had a realization: could this possibly be caused by windows?

I’m not certain, but would you mind testing the new version on Windows? The official Windows stable version was released yesterday. https://zed.dev/windows

[mollyvita]

while trying things out, i had a realization: could this possibly be caused by windows?

I’m not certain, but would you mind testing the new version on Windows? The official Windows stable version was released yesterday. https://zed.dev/windows

all the testing was done on latest preview version from there (0.209.0), this still happens :(

[mollyvita]

it's been a while and i even moved to linux yet this thing keeps happening 😭

https://github.com/user-attachments/assets/fd4deb5b-ab97-4015-8162-79992387da47

happens on 0.216.0+preview.88.e55a8c9cb1756058e653b3c2f65863dd10c46b58 latest extension ver (0.1.10)

[bestgopher]

Could you please check the Zed log?

[mollyvita]

of course!

got something even more interesting