PHP Language Server Output window re-opens after being manually closed #65
Comments
|
The extension/language server doesn't control when the output panel is opened. |
|
And thanks :) |
|
Log is as follows Is there a log file I should check? |
|
Help > Toggle Developer Tools |
|
|
Duplicate of felixfbecker/php-language-server#252 then. |
|
vendor/dojo-1.10/util/docscripts/lib/parser2/Parser.php |
|
Contents are identical to https://github.com/dojo/util/blob/master/docscripts/lib/parser2/Parser.php |
|
Also chokes on vendor/dojo-1.10/util/docscripts/lib/parser2/JavaScriptParser.php |
|
Hello, same here. Error on Thanks |
|
Looks like this has been fixed in the GO extension. Any chance we can have the same fix in this one? |
|
Looks like this issue has popped up again. I wasn't having it happen at all until today. Now it's opening the window every minute or so. |
|
Ditto. |
|
Can confirm this as well on Linux Mint 19.2. |
|
Same problem on macOS High Sierra. |
|
Same problem on macOS Mojave |
|
Which version are you on? |
|
Can confirm this issue too. |
|
Same here. Windows 10 (Version 1809) |
|
Only solution I've found so far is to disable PHP IntelliSense |
|
Well is there an error in the output panel? |
|
While watching the behavior, I came to the conclusion that the problem might be directly related to VS code. At least I don't get any error messages from the extension itself in the output. It just parses all PHP files and the output window gets the focus again sporadically, even if I'm typing in the terminal. It's strange that this only seems to happen with the PHP Language Server output. Does anyone come to the same conclusion? |
|
@TheCuda I have indeed the same! |
|
There is an option |
|
Same here. Windows 10 (Version 1903) I also disabled Xdebug from php.ini but the terminal still popping up.
|
|
@adummy832 your output specifically has an error in it, so it is not the same as discussed in the comments before |
|
Been having this bug too, output pane pops up unexpectedly and shows a lot of file parsing. If closed, it will open up again in about a minute and show more parsing. Whatever is going on seems to be pretty CPU heavy because my fans always turn on at about the same time. There are no errors in the VScode developer tools console. Windows 10 (Version 1809) |
|
@felixfbecker, After parsing all of my vendor files, those are the output i get on Someone already filed an issue on the actual vscode repo. |
|
According to this comment on the VSCode bug you can set the My guess would be that this extension is improperly marking some messages as @felixfbecker tracking down the root cause of this could be tricky, but would you be able to add a setting that would change the language server output open flag to |
|
Another helpful solution would be to provide config options (in the VSCode settings) to either include or exclude certain paths. Realize this would have to pass through to the actual language server project, but I didn't see options. We're doing some Wordpress dev and have an entire install open in VSCode. It'd be nice to say |
|
Yes, I had an error |
|
Experiencing the same error today. A new error as of the last few days or perhaps a recent update. VSCode Version 1.39.1. |
|
PHP Debug by FELIX BECKER extension was causing this issue for me. I uninstalled it, no more output panel and indexing messages. Just need to find something else to use. |
|
Hi Felix - We do have that Problem too - Output panel reopens serveral times while parsing projects - we do mostly Symfony, Wordpress and Typo3 projects: The errors occur mostly in the CMS/Framework folders: I do have several errors in the log. I've attached a file containing all errors + files causing the errors while opening an (older) Typo3-project. There are 6 files causing errors - the errors are repeating because of the symlinked nature of the typo3 installation. We'd prefer to keep parsing the framework/cms folders - a fix to prevent the language server to repeatably open up the output console would be nice - VSC is nearly unusable while parsing the files since the console is a massive attention-disturber :/ hope that helps - BR from Salzburg,
|
|
I'm seeing this as well – is there an option to just turn off this "parsing" nonsense? I don't need to see the full list of every file that's being parsed. |
|
This continues to be an issue with no solution purposed with other issues referencing this particular one. Why is this closed? Please review #454. Thanks! |
|
This is also affecting me, and I can see no solution besides just disabling this extension. |
|
Getting same thing here. Disabling this extension seems to be the only fix to keep it from annoyingly popping up every couple minutes. |
|
I have 3 issues with the author's various repositories, none of them have solutions. |
|
SOLUTION! |
|
Same problem |
1 similar comment
|
Same problem |
|
Same problem |
|
Any recommendations for extensions that work similarly without the same issue? I'm uninstalling and adding a review since this seems to be an ongoing issue that has been completely ignored. Not that it'll hurt but it's all I can do. Edit: Found Intelephense through a similar bug report that was also ignored. Adding it here for anyone who finds this through Google. |
|
As far as i can see this is the only VSC language server implementation for PHP: So we're stuck with it if want to develop PHP. Intelephense just extends the functionality and doesn't replace it: Pitty that felix doesn't seem to be able to react currently. |
|
Honestly just ignoring everything in |
|
LOL - But then you would have only code aids for your own code. Not the optimal solution if you program in the context of a framework (laravel,symfony,...) or a cms. Additionally you would not have code aids for composer dependencies, etc. that you would not push to git either ... I think the extension is good as it is - it only should not open the debug console if a php parse error occurs. I believe in a simple bug and no time on felix side ... |
|
I don't think felix is even aware that people are still commenting on this issue because it is closed. It would be helpful if somebody could open another issue and reference that here. This way he is aware that this issue still exists and how many people are still facing this issue. |
|
Solved by setting the following inside settings.json: edit: Never mind. It's back... |
|
#454 was merged. Hallelujah |
|
I'm facing the same issue, the output tab opens automatically and it's really annoying. |
and others
When analyzing files, the PHP Language Server Output window opens. After it is closed manually, it re-opens after a while. Also, it appears as though the PHP Language Server is continuously re-parsing the files in the project when it re-opens.
I am running:
PHP IntelliSense 1.0.0
Visual Studio Code
Version 1.9.0
Commit 27240e71ef390bf2d66307e677c2a333cebf75af
Date 2017-02-02T08:21:13.228Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0
Ubuntu Linux
uname -a gives
Linux vmuser-VirtualBox 4.4.0-62-generic #83~14.04.1-Ubuntu SMP Wed Jan 18 18:10:30 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Congrats on hitting v1.
The text was updated successfully, but these errors were encountered: