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

Client <n> quit with exit code 1 and signal 0 #798

Closed
2 tasks done
sq6er4 opened this issue Jun 14, 2023 · 14 comments
Closed
2 tasks done

Client <n> quit with exit code 1 and signal 0 #798

sq6er4 opened this issue Jun 14, 2023 · 14 comments
Labels
bug Something isn't working lsp LSP related issues needs:response Waiting for reply from the author

Comments

@sq6er4
Copy link

sq6er4 commented Jun 14, 2023

Version confirmation

  • Confirm

Following prerequisites

  • Confirm

Neovim version

NVIM v0.10.0-dev LuaJIT 2.1.0-beta3

Operating system/version

popos22.04

Terminal name/version

zsh

$TERM environment variable

No response

Branch info

main (Default/Latest)

Fetch Preferences

SSH (use_ssh = true)

How to reproduce the issue

Just after instaing.It happened in the c++ source program after i press 'i‘ and it kept poping up.

Expected behavior

I hope it becomes normal

Actual behavior

image

Additional information

No response

@sq6er4 sq6er4 added the bug Something isn't working label Jun 14, 2023
@ayamir
Copy link
Owner

ayamir commented Jun 15, 2023

rm ~/.local/state/nvim/lsp.log first, then reopen this file with nvim.

  1. Put the screenshot of :LspInfo.
  2. Put the content of ~/.local/state/nvim/lsp.log

@ayamir
Copy link
Owner

ayamir commented Jun 15, 2023

Also, check this: #559

@Jint-lzxy Jint-lzxy added the lsp LSP related issues label Jun 15, 2023
@ayamir ayamir added the needs:response Waiting for reply from the author label Jun 17, 2023
@sq6er4
Copy link
Author

sq6er4 commented Jul 1, 2023

rm ~/.local/state/nvim/lsp.log first, then reopen this file with nvim.

1. Put the screenshot of `:LspInfo`.

2. Put the content of `~/.local/state/nvim/lsp.log`

图片
This is my Lspinfo, and I have deleted lsp.log as your said.
I'm sorry for my late reply.

1 similar comment
@sq6er4
Copy link
Author

sq6er4 commented Jul 1, 2023

rm ~/.local/state/nvim/lsp.log first, then reopen this file with nvim.

1. Put the screenshot of `:LspInfo`.

2. Put the content of `~/.local/state/nvim/lsp.log`

图片
This is my Lspinfo, and I have deleted lsp.log as your said.
I'm sorry for my late reply.

@ayamir
Copy link
Owner

ayamir commented Jul 2, 2023

#559 (comment)

@ayamir
Copy link
Owner

ayamir commented Jul 2, 2023

This is my Lspinfo, and I have deleted lsp.log as your said.

remove lsp.log then reopen nvim, if this problem still exists then we can see the detail from the log.

@sq6er4
Copy link
Author

sq6er4 commented Jul 2, 2023

this screenshot is the result of following your steps

@Jint-lzxy
Copy link
Collaborator

@c8libur What we mean is "to use Neovim to open an arbitrary file" (e.g., nvim init.lua) instead of a folder (netrw); Then use:

nvim ~/.local/state/nvim/lsp.log

to obtain language client logs and paste ALL contents of this file here.

@CharlesChiuGit
Copy link
Collaborator

have u check if your nodejs version? which is used for copilot.
search the old issues if u need more guilds.

@DZRRRRRR
Copy link

DZRRRRRR commented Jul 7, 2023

SAME BUG!
I submit the SCREENSHOTS and the LSP.LOG file
image
image
lsp.log

@CharlesChiuGit
Copy link
Collaborator

CharlesChiuGit commented Jul 7, 2023

WHAT same bug, what exactly did u do? U haven't provide any useful info for us to debug.
U didn't done one single thing we told u to do. How on earth are we be able to help u???
Can u watch closely to what we told u to do?

@CharlesChiuGit
Copy link
Collaborator

CharlesChiuGit commented Jul 7, 2023

From the log file, it's seem like u provided the wrong nodejs version for copilot to execute. PLEASE check past related issues on how to fix it. U can also find related info in the repo wiki.

@ayamir
Copy link
Owner

ayamir commented Jul 7, 2023

SAME BUG! I submit the SCREENSHOTS and the LSP.LOG file image image lsp.log

Check your node version and ensure it > 16.x.

1688727630852

@CharlesChiuGit
Copy link
Collaborator

close as no further response.

@CharlesChiuGit CharlesChiuGit closed this as not planned Won't fix, can't repro, duplicate, stale Jul 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working lsp LSP related issues needs:response Waiting for reply from the author
Projects
None yet
Development

No branches or pull requests

5 participants