-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Vim/NVim freeze with GoDebugStop with Telepresence V2 #3432
Comments
I have two questions for you to help me better understand the situation.
|
No the log doesn't indicate |
That's odd. The only command that vim-go sends to delve that has Line 1605 in d34c629
Do you know what version of delve you have installed in the service you're connecting to with telepresence? |
So basically what Telepresence is doing it to route traffic going to k8 to your local machine. no need to setup delve in k8 pods. all you need is to run your service locally(in my example it's localhost:8090) and run telepresence to intercept calls from k8 and route them to your local port(in my example it routes to port 8090). therefore the delve is on my local machine not in k8 and my local delve version is the following:
|
I'm not quite sure what to make of this. I suspect it's related to the difficulties working with external processes in Neovim. Do you see the same problem with Vim? |
Same error with same log happens in Vim too. |
Do you see the problem only when telepresence is involved? I'm not able to duplicate what you're describing in a simple reproduction attempt, and I'm wondering if you could reduce the reproduction down to a simple case that that involves neither kubernetes nor telepresence and using a simple process. |
Is it possible that it might caused by deoplete.nvim because it's more nvim based than vim based and vim-go is vim based more than nvim. not sure. |
Doubtful, but if we're going to get to the bottom of this, then simplifying to a simple reproduction will be helpful. |
Ok sounds it's related to telepresence when I debug some simple code it works and I can stop debugging. |
Interesting. I suspect there's a race or message buffer handling error some place in vim-go's |
What did you do? (required: The issue will be closed when not provided)
I used telepresence to route proxy to my local for sake of local debugging a service hosted in k8. everything's fine till I call GoDebugStop then the entire vim/neovim freeze and I have to reopen the vim/neovim again. I'm using vim(8.1.3741) and neovim(0.4.3).
the error log is:
If possible, please provide clear steps for reproducing the problem.
What did you expect to happen?
What happened instead?
Configuration (MUST fill this out):
vim-go version:
1.26
vimrc
you used to reproduce:Vim version (first three lines from
:version
):VIM - Vi IMproved 8.1 (2018 May 18, compiled Feb 01 2022 09:16:32)
Included patches: 1-2269, 3612, 3625, 3669, 3741
Modified by team+vim@tracker.debian.org
Nvim version (first three lines from
:version
):NVIM v0.4.3
Build type: Release
LuaJIT 2.1.0-beta3
Go version (
go version
):1.18
gopls version
v0.9.1
The text was updated successfully, but these errors were encountered: