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

Apple Silicon M1 errors with Neovim-Lsp #1577

Closed
TC72 opened this issue Dec 31, 2020 · 2 comments
Closed

Apple Silicon M1 errors with Neovim-Lsp #1577

TC72 opened this issue Dec 31, 2020 · 2 comments

Comments

@TC72
Copy link

TC72 commented Dec 31, 2020

Describe the bug
When intelephense is configured to work with neovim-lsp it fails with an error output.

To Reproduce
Configure neovim-lspconfig with neovim 0.5 with native lsp support.
Starting neovim with a php file open generates errors in the lsp.log file, normally located at ~/.local/share/nvim/lsp.log
running :lua print(vim.inspect(vim.lsp.buf_get_clients())) returns an output of {}

Expected behavior
running the inspector should show lsp has succesfully attached to intelephense

Screenshots

[ ERROR ] 2020-12-31T09:15:48+0000 ] /usr/local/share/nvim/runtime/lua/vim/lsp/handlers.lua:265 ]
"Unhandled exception: MethodNotFound
Error: MethodNotFound
    at handleResponse (/Users/julianf/.cache/nvim/lspconfig/html/node_modules/vscode-jsonrpc/lib/common/connection.js:477:48)
    at processMessageQueue (/Users/julianf/.cache/nvim/lspconfig/html/node_modules/vscode-jsonrpc/lib/common/connection.js:292:17)
    at Immediate.<anonymous> (/Users/julianf/.cache/nvim/lspconfig/html/node_modules/vscode-jsonrpc/lib/common/connection.js:276:13)
    at processImmediate (node:internal/timers:463:21)"

Platform and version
M1 Mac Mini
macOS 11.1
NVIM v0.5.0-dev+6c2eb903a
~/.nvm/versions/node/v15.5.0/lib
├── intelephense@1.5.4
├── neovim@4.9.0
└── npm@7.3.0

Others have reported the issue fixed if they switch to node v12, this is not easy to do on an M1 Mac Mini and involves having some versions of Node running natively and v12 in Rosetta.

#1550 Someone has reported fixing issues with Apple Silicon by using intelephense.runtime to point to a version of node 15 built natively but I beleive this is what I have on my system.

@bmewburn
Copy link
Owner

Intelephense doesn't appear in the paths on the stack trace. Are you sure this is is from intelephense?

@bmewburn
Copy link
Owner

bmewburn commented Apr 3, 2021

Closing it's not clear that the error is coming from this extension.

@bmewburn bmewburn closed this as completed Apr 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants