-
Notifications
You must be signed in to change notification settings - Fork 217
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
Stdio mode broken since v3.0.0 #1695
Comments
I had the same issue when trying to use the builtin Neovim LSP client. I tried some older versions of the PowerShell Editor Services, release 2.5.3 works fine for me so far. Seems like this is broken since 3.0 |
Wow! Thank you, you're a genius :) 2.5.3 works perfect.
It looks like there was a major refactor, which broke it for stdio mode. |
Updated the title to be more specific |
I think it's probably #1592 Interestingly though, we have a suite of LSP and DAP tests which use PSES over stdio, and they work. So we'll have to dig into what exactly is still broken. |
Looking at that stack trace makes me wonder if we actually get into a command loop, since non-Code LSP clients don't usually start up an integrated console. 🤔 |
If it helps, Kate does have an integrated terminal, but only on Linux. |
Hm, does it work on Linux just fine? |
I have not tested it (don't have linux system). |
Just had a chance to test on Linux and got the exact same behavior. 3.1.2 and 3.1.3 lead to the error message from the original post, 2.5.3 works. |
I'm having the same issue using the Neovim LSP client and version 3.1.6 on Windows. Version 2.5.3 works just fine. Because I didn't set up the project before, I spend hours troubleshooting this thing until I found this issue... Since LSP is just starting to take off in many editors, it is actually a bit frightening that stdio clients have been broken for so long, with many releases in between. |
@jflepp We are still working on getting v3 "released" into its main consumer, the VS Code extension. Once that work is done, we're slated to come back and get the stdio mode working again too 😊 |
@andschwa Appreciate the work, thanks for the update 👍 Sorry if I came off a bit judgy / demanding, I was just a bit frustrated. It's now working in the 2.5 release and I'm having a blast working with PowerShell completely in the console 😊 But if I understand this correctly, does this mean that the versions 3.0.0+ are neither working in VSCode nor in stdio based editors? Maybe it would then make sense to mark them as pre-releases so that people don't get confused. |
3.0.0 is only in the preview channel for VS Code, and our top priority is to get that stable enough to release to the stable channel. So it's working (it uses named pipes) but we're working on sorting through our remaining MVP issues. |
Getting to work on this now! |
I think I got this solved! It was...a doozy. Had a few issues to fix. Tested successfully with eglot in Emacs. Will get a release out ASAP (today is the plan!) and hope you all can test in your various environments with different clients. |
Heyo, sorry, that took a bit longer to get out than expected due to client-side tests failing. @rashil2000, @fl3pp, @ydschneider Can you give v3.4.0 a try? |
Hi @andschwa, thanks for taking a look at the issue. Unfortunately, the version you supplied doesn't work, although a behavior change was noticeable. In the log of NeoVim
The configuration I'm running works flawlessly with version
|
Interesting...I have it working with Emacs and eglot with this configuration: (use-package eglot ; an LSP client in GNU ELPA
:hook
(powershell-mode . eglot-ensure)
:custom
(eglot-auto-display-help-buffer t)
(eglot-autoshutdown t)
(eglot-confirm-server-initiated-edits nil)
(eglot-connect-timeout nil)
:config
(add-to-list 'eglot-server-programs '(powershell-mode . ("pwsh" "-NoLogo" "-NoProfile" "-Command" "~/src/PowerShellEditorServices/module/PowerShellEditorServices/Start-EditorServices.ps1" "-BundledModulesPath" "/Users/andschwa/src/PowerShellEditorServices/module" "-Stdio" "-LogPath" "/Users/andschwa/src/pses.log" "-SessionDetailsPath" "/Users/andschwa/src/session.json" "-HostName" "Emacs" "-HostProfileId" "Emacs" "-HostVersion" "1.0.0" "-LogLevel" "Diagnostic")))) |
We figured it out! Fix incoming. |
Ok @fl3pp Can you please test https://github.com/PowerShell/PowerShellEditorServices/releases/tag/v3.4.1? I fixed that issue, but wonder if you'll find another! |
@andschwa didn't find anything, it just works! Thanks for fixing and have a nice weekend 😄 |
Yay! Thank you for testing!!! |
Hey all, I really didn't want this to happen again, so I've setup a full regression test against Eglot (an Emacs LSP client using PSES over stdio). |
Hi!
Kate is an awesome open source text editor made by the KDE folks, and it supports language servers. By default, they provide configurations for some popular languages, documented here: https://docs.kde.org/trunk5/en/kate/kate/kate-application-plugin-lspclient.html
I am trying to add PowerShell support in it, by using this config:
The server starts successfully, and recognizes symbols, but that's it. Nothing else seems to work, definitions go-to, hover etc. This is the log:
I'm using PowerShell 7.1.2 on Windows 10 21H2.
The text was updated successfully, but these errors were encountered: