Closed cprn closed 4 years ago
@cprn Can you turn on verbose so I can see CocInfo?
"Reading state from" happens in node_modules/intelephense/lib/intelephense.js
so I'm posting this upstream.
OK, so I was testing this some more to open a concise issue upstream and I found out Intelephense hangs on reading state only when I have intelephense.licenceKey
set in coc-settings.json
. It might only be happening when I'm behind proxy but can't confirm (I don't have unguarded environment at the moment).
I confirmed with Wireshark this is caused by Intelephense trying to connect to the license server directly (i.e. not respecting environment proxy settings). Ben Mewburn stated in this comment the value is taken from process.env.https_proxy
setting but there's no such thing in CoC's schema.json
and I have all the possible proxy-related variables set up in my ~/.bashrc
file. Also I never had to set up proxy in coc-settings.json
before and it was correctly detected from environment. I'm posting this upstream but leaving this issue open so that people could find it easily until it's resolved.
Can be closed, fixed upstream: bmewburn/vscode-intelephense#915.
Describe the bug On initialisation Intelephense fails after 2 minutes when trying to read the workspace state, even though at first it's empty. After timing out it properly re-indexes the project and saves its state. On next open it hangs again and this time doesn't write (probably because there are no changes). I just need a confirmation this isn't
vim
/coc-phpls
related before I open an issue upstream.To Reproduce Steps to reproduce the behavior:
vim
coc.nvim
coc-phpls
Expected behavior I expect Intelephense to load quickly, not hang while reading state and then timeout.
Screenshots Related parts of
:CocInfo
output:coc-settings.json
:Desktop (please complete the following information):
coc-phpls
: 2.1.4,Intelephense
: 1.3.5