-
Notifications
You must be signed in to change notification settings - Fork 511
Exception encountered starting EditorServices (DryIoc has waited for the creation of the scoped) #3462
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
Comments
Hi, Could you please provide more repro information? What code repository are you trying to use, what's your environment setup, what steps do I need to follow in order to reproduce this? Thanks! |
This issue is being closed as inactive, if this issue is still occurring it will be re-opened |
Hello, When I run vscode (v1.59 today), i open a simple file .ps1 with a --echo "test"-- inside. Nothing else. I'm on windows 1809 (enterprise 17763.1935). No update possible. Hard (or easy...) to explain how to reproduce this problem because, it appears when I start vscode directly with windows terminal (PowerShell Integrated Console v2021.8.0) or when I switch to this terminal from powershell terminal v7. The windows terminal doesn't start. Even if I reinitialize vscode, the problem remains. However, everything was working until this spring. If you need others logs, i can provide it |
Oops, sorry, didn't mean to let the bot close this. |
I really am not sure what's going on here, but the DryIoc package is a dependency of OmniSharp, so I'm trying to get it updated to its latest version (a bugfix release) in the hope that it may resolve your issue. |
This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information! |
Sorry, the bot got a little over-eager. We actually got DryIoc updated upstream in OmniSharp, and I was really hoping to land that in the latest preview, but it just barely missed the window. It will be in the next release though, so hopefully we can test soon and see if the updated package resolves it (the authors said "contains bugfixes!" so you know, 🤞). |
@anankee26 PowerShell Preview 2021.8.2 will be out in just a few minutes, would you test and confirm this issue has been fully resolved? It comes with that update to OmniSharp v0.19.4 (and so DryIoc 4.8.1 per OmniSharp/csharp-language-server-protocol#610) Thanks! |
Hello @andschwa , I disabled powershell 2021.8.0 and installed powershell preview 2021.8.2. VS code in version
Unfortunately, always an error when I start powershell windows 5.1. However, there are somes differences in the log with the previous:
|
That is super strange and thanks for the heads up. Perhaps those logs will help. Reproducing this has been super difficult. |
Was discussing this with @rjmholt and he has two ideas which are our best leads yet:
|
Out of nowhere I'm getting the same thing. Was literally working fine and I added a command to write some data to the terminal and I got this error:
|
@jutaylorREADI can you give more detail about the command you ran that caused this error? Can you also include your PowerShell version |
@jutaylorREADI I'm sorry, the error message is confusing due to the DryIoc library, it actually has nothing to do with this. In your error, the important part is this:
Could you please file a new issue using our bug report template so we can triage it appropriately? Thank you! |
@anankee26 Could you please try the latest Preview extension and let me know if your original issue still repros? |
Hi @andschwa Enclosed logs files. logs Powershell preview v2021.11.1.txt thanks for the following ! |
Hi, have you found a solution ? thank you |
Nope, haven't found a solution yet. There's not been an easy way to repro this, and it seems like an issue between OmniSharp's LSP library and dependencies of PowerShell 5.1 😢 |
I have the same problem with PS 5.1 and 7.... |
Hi, For me, it has been resolved by a new OS... I was working on windows 1809 et now on windows 22H2 with an installation from scratch. So Vscode, vscode-powershell, and windows powershell 5.1.19041.1320 (and core v7.2.1) work perfectly together for the moment. |
This particular error is actually a number of issues that appear similar, please open a new issue will full information if you are still seeing this...thanks so much! |
Hi, |
Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead. |
The solution I found was I had to reinstall 7.1, Windows PowerShell was no longer sufficient, even though it was selected in the VS Code settings. |
Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead. |
I installed the PowerShell Preview extension v2022.3.1 and this issue has been resolved |
Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead. |
This error started occuring for me after I upgraded my Powershell to Core 7.2.5.
(1) Fixes the issues that were originally reported (the big stack trace error messages), while (2) fixes the next issue I had, which was the Powershell Language Server seemed to be hung (without error, I didn't wait 100 years to see if it would time out). Note that the recommended setting ${fileDirname} also caused issues. EDIT: |
Thank you for your comment, but please note that this issue has been closed for over a week. For better visibility, consider opening a new issue with a link to this instead. |
@efd7887 this is an official warning to please abide by our Code of Conduct, keep discussion civl, and avoid personal insults. |
hello,
With reference to Originally posted by @anankee26 in #3297 (comment)
Powershell Windows terminal 5.1 doesn't start in vscode but ok with PS 7.1
with the powershell add-on in 2021.6.2
This message that appears in the terminal at startup:
and in editorservices.log
and in vscode-powershell.log
Output terminal:
Thanks for support.
The text was updated successfully, but these errors were encountered: