-
Notifications
You must be signed in to change notification settings - Fork 513
LSP services fail with non-ASCII characters in paths #2324
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
LSP services fail with non-ASCII characters in paths #2324
Comments
@Silver-Fang thanks for opening this issue and providing screenshots. I am having some trouble reproducing this issue but the issue may be do to performance issues we sometimes see in the PowerShell extension i.e. the completions are so slow that it appears they are not coming at all...I would be curious to see if you are able to reproduce this in the PowerShell Preview extension? We recently merged 6+months of stability/performance improvements into preview, and are hoping to ship those in our "stable" PowerShell extension in January. It would also be good to know if you are able to get any other features of the extension working with PS7 i.e. are you able to run code using F8 in the integrated terminal...if not or you are hitting other errors/failures logs would be very helpful...thanks! |
@Silver-Fang you should be getting completions in PS 7 the same as you see with PS 5.1; what you're seeing looks like a bug. If you're able to attach your logs here, we might be able to determine the cause of the issue. |
logs.zip |
Seeing this in one of the logs:
|
And here:
That explains the lack of completions |
Would you be able to provide the path of the file you're trying to complete in? Alternatively, if you can provide the payload logs, that will show the contents of the LSP messages PSES is being sent causing it to crash. |
I got it. It's because of non-ansi characters in the path.
If I use a path like D:\Completion.ps1, it works just fine. |
Hi @Silver-Fang, can you follow the steps on uploading payload logs? That will help us understand if it's PS Extension or VSCode. |
@Silver-Fang would you also be able to provide one of the paths in the log in its non-url-escaped form? |
Thanks! |
It's interesting... that does come in correctly at first:
but the AbsoluteUri seems a bit odd... |
Ah hah... This issue is in PowerShell Editor Services... The problem is that we are calling ToString on a Uri and then parsing it again with Here's the repro:
|
Unfortunately there's more here... the Omnisharp library we depend on uses |
Under PS5.1 mode, typing "Get-" triggers a list of commands starting with that.


However, with PS7.0, nothing happens:
What's wrong here?
The text was updated successfully, but these errors were encountered: