-
Notifications
You must be signed in to change notification settings - Fork 147
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using wrong wakatime-cli binary file name on Linux arm64 #216
Comments
I have identified an issue with the aforementioned build of VSCode: by default, when installing the plugin, it installs a x86_64 one instead of arm64, even when on arm64. So VSCode probably mistakenly pulls the intel/amd one. Maybe it has something to do with the insiders build, though. |
It took a minute, but I came up with a sneaky workaround for this issue by forcing the arm64 executable by locking out the extension from updating. On each launch, it updates itself and the CLI, right? well, as I mentioned here:
It downloads the x86_64 one for some reason, even when on arm64. Downloading the arm64 one manually works, but gets overwritten when the plugin updates the CLI. So I prevented VSCode from accessing the binary (I chowned it to root), so it couldn't be overwritten. Now it's working and sending out heartbeats correctly. Please include a check into the plugin that verifies the current arch. For example, gcc is capable of that. Thanks |
The wakatime plugin uses os.arch() to detect |
Could you please:
|
On it. |
symlinking didn't work, I had 'missing modules', however, copying worked. Hmm, it outputs |
Why are you doing this? vscode-wakatime/src/dependencies.ts Lines 113 to 125 in 7ab65d7
|
The problem seems to be that the latest arm64 binary is not being detected as the latest when polling the version value from GitHub. Still, that doesn't explain how we got from arm64 to x86_64. |
We currently have two wakatime-cli implementations. The new Go one and the legacy Python one. We download both so we can test the new Go one but fallback to the more stable Python one if the Go one errors. |
Can you turn on debug mode in the wakatime plugin settings, then open the vscode dev console and reload. Then paste the logs here? |
@alanhamlett Look at the original post, the three code blocks there are the erroneous output. Thanks |
Here is the full output:
|
The issue is in vscode, where it's downloading the correct Linux arm64 wakatime-cli binary but then using |
We can't just use the raw output from @simonSlamka can you also add this line after the current
|
os.arch() returns a string |
@simonSlamka you have the legacy python wakatime-cli disabled in your |
We had the new Go wakatime-cli disabled when sending heartbeats, but we still used it when fetching status bar code stats. Fixed with f56f87d. |
@alanhamlett no, not explicitly. the version is v1.18.9, by the way |
Restarting vscode should fix it for you. However, the problem will return once we re-launch the new Go wakatime-cli. To fix this for later, you'll have to re-do the symlink from this comment then add these console.log lines to
And let me know the output in your vscode dev console after reloading. |
I pulled from origin and rebuilt, then copied the extension to the vscode dir. Still the same problem, it seems. Even the output is identical. (except for the two |
Yes, my next comment clarifies. I've deleted that wrong comment, you can ignore it since it's not correct. |
I found the problem, it's because the legacy wakatime-cli doesn't support arm! You should enable the new Go wakatime-cli with this line in your
Also, make sure to update the extension to v14.0.3 (latest version in the marketplace released Today) and restart VS Code. Can you see if that fixes it for you? |
ok @alanhamlett it's fine now, i did what you said. Thank you very much to find and fix the problem. |
Nothing will be needed in the future, as this just enables the beta wakatime-cli before it's launched to everyone. When it's launched, the config change won't be needed anymore but it won't hurt to leave it there. |
Got it. |
Hello,
I'm experiencing unexpected behavior in my vscode with the wakatime extension. I have confirmed that my API key is correct.
The log in the home directory is empty.
Repro is to just install the extension, input your API key and get it to attempt to sync.
VSCode:

VSCode console says the following:
Furthermore, it reports the following:
At the end, it says this:
As I said, the log mentioned above is empty.
The text was updated successfully, but these errors were encountered: