Vscode-intelephense: 1.0.2 "Failed to apply changes to file://"

[JohannesMattsson91]

Getting this error in the output:

[Error - 3:04:03 PM] Failed to apply changes to file:///srv/www/....

I'm using Linux nad have had this issue since yesterday (I think)

[JDDoesDev]

Watching: I just ran into this on macOS, v1.31.1

[north-krimsly-hp]

I'm getting the same error as well, on Mac OS 10.14.2. It started happening when I modified a comment like this '/* */' to this syntax '//'. But now it won't go away. I had to disable the extension.

[geisels]

Same error on Linux Mint 19.1, Cinnamon, VS-Code 1.31.1, Intelephense 1.0.2.

[akanaka]

Same error on Linux Mint 18.3, Cinnamon, VSC 1.31.1, Intelephense 1.0.2.

[korandcom]

Same error on Windows 10 and seems it's appears only if single file opened outside the workspace.

[jnettik]

Same. I re-enabled the extension after the 1.0.2 release but I'm still not able to edit files, getting the error above. Disabling the extension for now.

[bmewburn]

Are these files over 1MB?

[jnettik]

The one I'm working on now is 16k.

[bmewburn]

Haven't been able to accurately repro this yet. I have seen it happen in response to a previous server crash. Also there was a chance that it may have been kicked out of the document cache unexpectedly which is now prevented. Is it still occurring in 1.0.3?

[ChanJuiHuang]

In my vscode, it is fixed^^

[korandcom]

Not fixed for me on 1.0.3. To reproduce you need to close all folders in VS Code and open single file from Windows Explorer for example. If you try to edit something in this file - on every single key press "Failed to apply changes to..." message appears in output log for Intelephence extension.

[JDDoesDev]

I'm still getting errors. The trace shows this

[Trace - 9:17:44 AM] Sending notification 'textDocument/didChange'.
Params: {
    "textDocument": {
        "uri": "file://...",

__EDIT: After going to "Manage Extension" it showed "Reload Required". I had already reloaded once, but it seems that it didn't take so for 1.0.3 be sure to reload your window a couple times to be safe.__

[jnettik]

I've updated and refreshed a few times. 1.0.3 seems to be working for me now.

[korandcom]

In 1.0.3 version output window didn't pop up automatically but errors still appears in log.

[bmewburn]

yeah, I should have mentioned it's a warning now instead of an error so it's less annoying.

[bmewburn]

Might be fixed by #317