Closed moyotar closed 6 years ago
@abingham @ptrv Sorry for disturbing you. What's the reason of this problem? curl
, url-retrieve
or emacs-ycmd
? Is there a way to solve it now?
I'm sorry, but I really don't know. I don't have a Windows machine on which to test it, and as far as I know you're the only person experiencing this problem. I really wish I could help, but I don't know what else I can do right now.
For what it's worth, I suspect that this is not a problem specific to emacs-ycmd (though we may be part of the problem somehow).
On Wed, Aug 16, 2017, 08:41 moyotar notifications@github.com wrote:
@abingham https://github.com/abingham @ptrv https://github.com/ptrv Sorry for disturbing you. What's the reason of this problem? curl, url-retrieve or emacs-ycmd ? Is there a way to solve it now?
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/abingham/emacs-ycmd/issues/442#issuecomment-322774441, or mute the thread https://github.com/notifications/unsubscribe-auth/AAE1eKVQLdedh6IERxLvsxEUwmx9IDdpks5sYvF6gaJpZM4O1bOA .
Thanks! There's a new discovery that I can reproduce the error above with curl
used. To more accurately, when I use projectile-kill-buffers
to close current project(python
), ycmd
will be closed and buffer *ycmd-server*
will be killed too. Then, after I enter an other project(python
) and restart ycmd
, many connections as picture shows above will be produced quickly.
Oh, if I close ycmd
firstly before using projectile-kill-buffers
, the error will not take place. I don't know these whether it's helpful.
With
ycmd
running a little time, I met similar error no matter which request backend I chose,curl
orurl-retrieve
. Now when meeting this error, I have to kill emacs and reopen it to make it serves normally.And there are two issues reference for more info about error.
440