Using wrong wakatime-cli binary file name on Linux arm64
See original GitHub issueHello,
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:
[WakaTime][ERROR] /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: �7@8@@@@@@��@@@@�u�u: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ��: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ��@@DDP�td�e�e@�e@ttQ�td/lib64/ld-linux-x86-64.so.2GNU: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: +Pz: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: cannot create E@@�u�uXHzlibdl.so.2_ITM_deregisterTMCloneTable__gmon_start___Jv_RegisterClasses_ITM_registerTMCloneTabledlsymdlopendlerrorlibz.so.1inflateinflateInit_inflateEndlibc.so.6__stpcpy_chk__xpg_basenamemkdtempfflushstrcpyfchmodreaddirsetlocalefopenwcsncpystrncmp__strdupperrorclosedirftellsignalstrncpymbstowcsforkunlinkmkdirstdingetpidkillstrtokfeofcallocstrlenmemsetdirnamermdirfseekclearerrunsetenv__fprintf_chkstdoutstrnlenfclose__vsnprintf_chkmallocstrcatrealpathraise__strncpy_chknl_langinfoopendirgetenvstderr__snprintf_chk__strncat_chkexecvpstrncat__realpath_chkfilenofwritefreadwaitpidstrchr__vfprintf_chk__strcpy_chk__xstat__strcat_chksetbufstrcmp__libc_start_mainferrorstpcpyfreeGLIBC_2.2.5GLIBC_2.3GLIBC_2.4GLIBC_2.3.4: File name too long/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ELF: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: Syntax error: word unexpected (expecting ")")
Furthermore, it reports the following:
[WakaTime][ERROR] Error: Command failed: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli --entity /home/simtoon/terminalInsanityCLI/terminalInsanityCONSOLE/zshVerify --plugin "vscode/1.59.0-insider vscode-wakatime/14.0.0" --alternate-project terminalInsanityCLI/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: �7@8@@@@@@��@@@@�u�u: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ��: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ��@@DDP�td�e�e@�e@ttQ�td/lib64/ld-linux-x86-64.so.2GNU: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: +Pz: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: cannot create E@@�u�uXHzlibdl.so.2_ITM_deregisterTMCloneTable__gmon_start___Jv_RegisterClasses_ITM_registerTMCloneTabledlsymdlopendlerrorlibz.so.1inflateinflateInit_inflateEndlibc.so.6__stpcpy_chk__xpg_basenamemkdtempfflushstrcpyfchmodreaddirsetlocalefopenwcsncpystrncmp__strdupperrorclosedirftellsignalstrncpymbstowcsforkunlinkmkdirstdingetpidkillstrtokfeofcallocstrlenmemsetdirnamermdirfseekclearerrunsetenv__fprintf_chkstdoutstrnlenfclose__vsnprintf_chkmallocstrcatrealpathraise__strncpy_chknl_langinfoopendirgetenvstderr__snprintf_chk__strncat_chkexecvpstrncat__realpath_chkfilenofwritefreadwaitpidstrchr__vfprintf_chk__strcpy_chk__xstat__strcat_chksetbufstrcmp__libc_start_mainferrorstpcpyfreeGLIBC_2.2.5GLIBC_2.3GLIBC_2.4GLIBC_2.3.4: File name too long/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: ELF: not found/home/simtoon/.wakatime/wakatime-cli/wakatime-cli: 1: /home/simtoon/.wakatime/wakatime-cli/wakatime-cli: Syntax error: word unexpected (expecting ")")
At the end, it says this:
[WakaTime][ERROR] Unknown Error (2); Check your /home/simtoon/.wakatime.log file for more details (at t.Logger.log (/home/simtoon/.vscode-insiders/extensions/wakatime.vscode-wakatime-14.0.0/dist/extension.js:2:723869))
As I said, the log mentioned above is empty.
Issue Analytics
- State:
- Created 2 years ago
- Comments:25 (12 by maintainers)
Top Results From Across the Web
How can I resolve the error "cannot execute binary file"?
Usually that error message means Linux doesn't recognize the file as a shell script or as an executable file. Typically the cause is...
Read more >"No such file or directory" error when executing a binary
The answer is in this line of the output of readelf -a in the original question [Requesting program interpreter: /lib/ld-linux.so.2].
Read more >What makes grep consider a file to be binary?
I'm using cygwin to grep through them. These appear to be plain text files; I open them with text editors such as notepad...
Read more >Ask Question
How do I resolve an error when attempting the "opam init" command? 0 · bash: ./flash_tool: cannot execute binary file: Exec format error...
Read more >Provide precompiled binaries for ARM #861 - prisma ...
I've managed to cross-compile aarch64 (arm64) binaries (with some ... Error: Unknown binaryTarget linux-arm-openssl-undefined and no custom ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
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
~/.wakatime.cfg
file: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?
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.
https://github.com/wakatime/vscode-wakatime/issues/216#issuecomment-882106515
(except for the two
console.log
’s we added)