Skip to content
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

rust remote server 失败,可能是在远程主机没有启动 tabnine #944

Closed
getong opened this issue May 14, 2024 · 7 comments
Closed

Comments

@getong
Copy link
Contributor

getong commented May 14, 2024

启动报错:

--- [16:02:28.263397] Client connect from 192.168.31.70:40908

--- [16:02:28.678724] init_search_backends finish

--- [16:02:30.889491] wait for init_search_backends to finsih execution

看 lsp_bridge.py 代码:

    # Functions for initialization
    def init_search_backends(self):
        # Init tabnine.
        self.tabnine = TabNine()

        # Init codeium
        self.codeium = Codeium()

        # Init copilot
        self.copilot = Copilot()

我 ps aux | grep -i tabnine , 没发现 tabnine 在远程主机运行。
但我在远程主机单独启动 emacs,是能够补全的, 也发现 tabnine 进程在运行。
综上,很可能是这段代码在远程主机上没有启动 tabnine 导致的。

@manateelazycat
Copy link
Owner

远程编辑应该是没有适配 TabNine 的

@manateelazycat
Copy link
Owner

大佬有精力可以帮忙看一下, 欢迎发PR

@manateelazycat
Copy link
Owner

@getong 目前是从 tabnine-bridge-binaries-folder 变量中读取TabNine的值, 并在

executable_path = os.path.join(version_path, distro_dir, TABNINE_EXECUTABLE)
获取 TabNine 的值。

需要给出 tabnine-bridge-binaries-folder 的值和服务器上 TabNine 的路径, 然后我们再看看怎么修复。

@getong
Copy link
Contributor Author

getong commented May 17, 2024

(tabnine-bridge-binaries-folder (expand-file-name "~/.backup-emacs/tabnine-bridge/tabnine-binaries"))

我加了打印,但没执行到executable_path, 输出错误信息跟上面的一致。

@manateelazycat
Copy link
Owner

你在服务器端是怎么启动 lsp-bridge 的?

@getong
Copy link
Contributor Author

getong commented May 17, 2024

python3 ~/.emacs.d/var/straight/repos/lsp-bridge/lsp_bridge.py

@manateelazycat
Copy link
Owner

应该是不知道什么原因

self.lsp_bridge.init_search_backends_complete_event.set()
这行代码没执行

@getong getong closed this as completed Jun 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants