-
Notifications
You must be signed in to change notification settings - Fork 34
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
Failed to launch Coq. #241
Comments
In case it helped, I tried to use
Here is the log generated by |
In case of doubt, reboot... Now things looks ok. I'll monitor this today. Please tell me if anything in the log looks suspicious |
Thanks for the detailed report. Nothing stands out to me in the log, but if it starts happening again running |
No problem today either. I really feel something was wrong with my mac and reboot fixed it. Closing as it is more likely a mac issue that CoqTail. |
Glad it's working now. Feel free to reopen if it happens again.
It creates a temporary file whose path is stored in |
Happened again today (after only one day of uptime). I tried |
Sorry, what I meant is
Something like that is definitely possible. Something I suggested before to help diagnose a similar problem was, when you start encountering the problem, run If that part's working and the debug log doesn't show anything useful then my only other thought is to sprinkle Does this issue start the first time you try to use Coqtail after reboot, or does it work for a while and then suddenly stop launching the next time you try? |
it works for a (random) while and stops working. reboot fixes it |
It's happening again, I'm investigating:
I never used vimscript or plugin, so any advice on where to add |
The log path is in As for
Additionally on Line 195 of Finally on Line 329 of |
None of my print in python code showed up. I tried line 329 of coqtail.vim and it shows |
I left vim/coq for a meeting and when I was back, I managed to run Coqtail correctly, and now it won't start again. Still more questions :D |
Since |
this should be informative |
Ok so the problem is Vim isn't able to connect to the Python server. That's either because the server is going down or something is blocking the connection. I just merged a change that will print a bit more information about this error. If you pull the most recent version then next time it happens you should see |
Nice addition, thank you
I'm not familiar with port debugging, I'll see what I can find EDIT1:
This is the vim I have opened and where If I close it, nothing is reported anymore and
|
So it looks like the server is up, but the Vim channel is timing out when connecting to it. I'm not really sure where to go from here. A somewhat similar issue was fixed by doing something to Just as a sanity check, when it starts failing, with Vim still open (so the Python server doesn't shut down), try |
I just tried the two I waited a bit with |
It's very strange and unfortunately I'm out of debugging ideas. I'll leave this issue open in case someone encounters the same problem or if there are new developments. As a workaround you might try using NeoVim. Coqtail uses a slightly different approach for the NeoVim-Python communication so maybe it won't have this same issue. |
Never used NeoVim, that might be a good opportunity to do so ;) |
I installed neovim today. I have a setup where vim can't start the plugin but nvim is fine :D |
I am encountering the same issue. With Vim 9.15 on M1 Mac mini I fixed it by restarting my Mac. It might be a problem with OSX |
Sorry to hear this is still going on. I don't have a Mac to test with, but I'm happy to help as best I can if you think of any other ways of diagnosing the problem. |
Hi ! I'm getting this message for a few days now (didn't change anything. Same version of vim/plugin/opam/ocaml/coq).
It seems to randomly start (and once started, it works alright).
I don't know how to get more diagnostic or try to debug this. How can I get more information on what failed ?
OS: MacOS Monterey 12.0.1
vim: VIM - Vi IMproved 8.2 (2019 Dec 12, compiled Sep 16 2020 23:47:44)
opam: 2.0.6
ocaml: 4.12.0
coq: 8.13.2
The text was updated successfully, but these errors were encountered: