Skip to content

[BUG]Failed to ensure Node runtime: Node installer failed: Acquiring lock... #208

@htammen

Description

@htammen

Describe the bug
When I start neovim or run the commands ":TabnineChat" or ":TabnineAgent" I get the following error.

 Error 16:36:26 notify.error Failed to ensure Node runtime: Node installer failed: Acquiring lock...
Lock acquired.
Platform: linux-x64
Downloading https://update.tabnine.com/update/nodejs/v24.12.0/linux-x64.tar.gz...
Error: https://update.tabnine.com/update/nodejs/v24.12.0/linux-x64.tar.gz: status code 403

I installed the newest tabnine-nvim plugin into my lazyvim installation. Then I had to install newest cargo and rustc versions to be able to build the binaries in webview directory.

cargo --version
cargo 1.93.1 (083ac5135 2025-12-15)

rustc --version
rustc 1.93.1 (01f6ddf75 2026-02-11)

To Reproduce
Don't know

Expected behavior
Error should not happen and Tabnine Chat/Agent window should display a prompt.

Version Info:

  • OS (try cat /etc/os-release):

cat /etc/os-release
PRETTY_NAME="Ubuntu 24.04.3 LTS"
NAME="Ubuntu"
VERSION_ID="24.04"
VERSION="24.04.3 LTS (Noble Numbat)"
VERSION_CODENAME=noble
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=noble
LOGO=ubuntu-logo

  • Neovim version (nvim -v):

nvim -v
NVIM v0.12.0-dev-1742+gad438b6b14
Build type: RelWithDebInfo
LuaJIT 2.1.1764270282
Run "nvim -V1 -v" for more info

  • Installed Tabnine Binaries (ls -A /path/to/plugin/binaries):

ls -A -- "$(nvim --headless -c 'lua io.stdout:write(vim.fn.stdpath("data"))' -c qa)"/*/tabnine-nvim/binaries/
4.321.0

  • Active Tabnine Binaries (cat /path/to/plugin/binaries/.active):

cat -- "$(nvim --headless -c 'lua io.stdout:write(vim.fn.stdpath("data"))' -c qa)"//tabnine-nvim/binaries/.active
cat: '/home/helmut/.local/share/nvim/
/tabnine-nvim/binaries/.active': Datei oder Verzeichnis nicht gefunden (File or directory not found)

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions