You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is /home/user/test.php a real path or one you sanitised? as it would be very unusual to be working in the root of your home directory...
I assume test.php is a standin for the file your actually working on and the path is the path to that file? in which case, assuming that it's open, it would be very strange that this error is reported 🤔
I mean, it's not moot if it's not the file you have open in your editor when you apply the fix - is it the very same file you have open in your editor?
Does the error go away when disabling that linter?
That error would happen if the IDE is requesting a code action on a file that has not been registered with the language server, or if the file was previously closed.
We could possibly bury these errors or relegate them to warnings - but it would be good to know under which circumstance this can happen.
There is not, I don't personally maintain the VS code extension, I'll ping the maintainer. You could also try installing Phpactor independently and updating the extension to point to it instead of depending on the version that's "distributed" with it.
I mean, "is worse than ever" does that relate to the issue raised by @bilogic on the vscode repo: phpactor/vscode-phpactor#254 which seems to be a different issue. are the "stream has already been closed" errors being shown as per this ticket?
The underlying problem that these 2 issues and several others are:
the destruction of user experience through high frequency (every 2-3 minutes) alerts which are unactionable (because they are vague and makes no sense to me as a user)
Activity
dantleech commentedon Nov 19, 2025
is
/home/user/test.phpa real path or one you sanitised? as it would be very unusual to be working in the root of your home directory...I assume
test.phpis a standin for the file your actually working on and the path is the path to that file? in which case, assuming that it's open, it would be very strange that this error is reported 🤔bilogic commentedon Nov 19, 2025
It is a sanitized one but that is quite moot here, is there an option to silence this distraction? Or find determine the actual cause?
dantleech commentedon Nov 19, 2025
I mean, it's not moot if it's not the file you have open in your editor when you apply the fix - is it the very same file you have open in your editor?
Does the error go away when disabling that linter?
That error would happen if the IDE is requesting a code action on a file that has not been registered with the language server, or if the file was previously closed.
We could possibly bury these errors or relegate them to warnings - but it would be good to know under which circumstance this can happen.
bilogic commentedon Nov 19, 2025
pinteach time I save itpint, will get back thanksbilogic commentedon Jul 27, 2026
I still keep getting this every other minute.. here are logs
dantleech commentedon Jul 27, 2026
This is on VS code? This bug looks similar and was fixed in #3059 and released but still waiting for a new VS code version cc @zobo
bilogic commentedon Jul 27, 2026
Correct, vscode
bilogic commentedon Jul 30, 2026
Is there a nightly build?
dantleech commentedon Jul 31, 2026
There is not, I don't personally maintain the VS code extension, I'll ping the maintainer. You could also try installing Phpactor independently and updating the extension to point to it instead of depending on the version that's "distributed" with it.
dantleech commentedon Aug 2, 2026
I think a new version has been tagged now.
bilogic commentedon Sep 6, 2026
Sorry, but It is worse than ever
zobo commentedon Sep 7, 2026
I'll revisit this an maybe hide the error on the extension side
dantleech commentedon Sep 7, 2026
I mean, "is worse than ever" does that relate to the issue raised by @bilogic on the vscode repo: phpactor/vscode-phpactor#254 which seems to be a different issue. are the "stream has already been closed" errors being shown as per this ticket?
bilogic commentedon Sep 7, 2026
The underlying problem that these 2 issues and several others are:
the destruction of user experience through high frequency (every 2-3 minutes) alerts which are unactionable (because they are vague and makes no sense to me as a user)
Also unactionable/unexplainable:
phpactor(worse.unresolved_name)#2953phpactor(worse.assignment_to_missing_property)#2998And if I may say so, sometimes also unsure if it is extension or php-actor itself
It is better to fix the way these errors are reported to the right fixer instead of fixing each error (because there are so many)