-
Notifications
You must be signed in to change notification settings - Fork 185
Connection to server got closed. #326
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
Comments
I can provide a bit more information about this, and probably a mean to reproduce the problem : it happens on 3 different projects when trying to parse /api/api-field.php from the ACF WordPress plugin. As a workaround, i've changed the |
Hello Alenore, |
I just copy the custom post type code from ACF, and CPT ui and pasted it to the functions.php than removed these plugins from WP. Finally the Intellisense extension works, so thank you Alenore! |
@designcraft I wouldn't advice you to do that, as it's going to pain to support ACF updates over the time. |
@Alenore @designcraft If you want painless future updates and have time to look at this, why not just do a PR? :) |
@felixfbecker The main reason why I didn't do a PR is, my fix is an ugly one :p It doesn't really fix the source of the problem (why the function returns null in the first place, instead of correctly matching the type), just returns a Types\Null_ when it could possibly be something else. |
It just seems like you all are willing to invest so much time in the workaround, so just wanted to remind that this is a community project and anyone can find the real fix and submit it ;) |
Hi there, chiming in here since this seems to be the issue that's closest to what I'm seeing I've got a php process at 75 or even 95% at times
all I get from the console is
How would I go about getting more infos? in my case too the WP ACF plugin is involved the parsing stops at hope I can bring some more infos but I'd need guidance to do so thanks a lot |
I have got same error my stack trace:
I have found, that a returned value |
from issue felixfbecker#326
Hi @Sensirex I'm curious where you got that stack trace from though and maybe you can submit a PR as it seems a good fix thanks again |
go to help - toggle developer tools - go to console (on windows version) and now you can view here all messages(traces, errors and etc.) |
many thanks
let me know if you have time for the PR
if not I'll try to find time to do it
…On Thu, Mar 16, 2017 at 9:16 AM, Sensirex ***@***.***> wrote:
go to help - toggle developer tools - go to console (on windows version)
and now you can view here all messages(traces, errors and etc.)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#326 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABbyTmG5h5KnDPihMdai_76WMR9Qng7uks5rmO_1gaJpZM4MQzKM>
.
|
I already had added a commit :) |
my bad,
missed it in the thread ...
thanks!
it's really nice to be able to use this again :)
…On Thu, Mar 16, 2017 at 9:33 AM, Sensirex ***@***.***> wrote:
I already had added a commit :)
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#326 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABbyTrYTVwwtEM2UQ9oRvwKs0nTZLGecks5rmPPggaJpZM4MQzKM>
.
|
I just installed 1.2.0 and I'm getting this same problem on line 466 of DefinitionResolver now. I don't know how to tell why the specific file that kills it every time is causing that problem. For now I fixed it with this code but I'm not sure that is the right way to fix the problem:
|
No, it's not. |
@cardonator I have version 1.2.0 and got the same exact error on line 466 in src/DefinitionResolver.php. I believe this is the same issue in #286 . The error is gone after changing all occurrences of:
to:
@felixfbecker According to your last comment this seem not to be a good fix to the problem. May be this is already in your plate. I am looking forward to see a fix come out. |
I can tell you the exact thing that is killing my file, it's this code right here:
|
I said numerous times before, the issue is not that the |
@felixfbecker that's fair. I didn't realize another better fix was in the works. I don't really mind a cheap manual fix when it will be fixed permanently later. |
I'm unsure if the cause of my error is the same as any of the above, but basically the vendor folder of my Laravel project is crashing the language server. This doesn't happen without the vendor folder. Here's the output. vscode: |
Just a heads up to everyone watching this thread: The latest Version of PHP Intellisense (1.2.1) contains a fix for this bug. I would like to know if the problem persists or if it is fixed for all of you. |
It's definitely fixed for me! |
Definitely fixed for me, I'm noticing a lot of files in my project are larger than the max size limit. Is there a way to override that value? |
Hi,
VS Code: 1.10.1
Node: 6.5.0
PHP extension pack: 1.0.0
Php intellisense: 1.1.3
I have this problem since installed the extension, server got closed and will not be restarted after 5 crash.
Console log:
extensionHost.ts:282 [Extension Host] TypeError: Return value of LanguageServer\DefinitionResolver::resolveExpressionNodeToType() must implement interface phpDocumentor\Reflection\Type, null returned in C:\Users\Varga S�ndor.vscode\extensions\felixfbecker.php-intellisense-1.1.3\vendor\felixfbecker\language-server\src\DefinitionResolver.php:445
Stack trace: ....
The text was updated successfully, but these errors were encountered: