-
Notifications
You must be signed in to change notification settings - Fork 107
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
Request initialize failed with message - scheme is missing #602
Comments
Granting full disk access to VSCode did not resolve. |
Same problem here for me too. |
Other than the message popping up, what else happens? Do you still have IntelliSense/auto-completion? |
No, I do not. |
Same issue here |
No IntelliSense. The only completions offered are words that already exist in the file. |
For those who are seeing this, what OS are you using? |
Windows 11 [Version 10.0.26100.2314] |
Windows 11 Pro for Workstations, version 24H2, build 26100.2314. |
And can I also get the output from the |
1.249.0 was released last night. I'm curious if any of you are still seeing this error - mostly because we didn't introduce any changes in this area for the previous 1.247.1 release, so I'm wondering if it'll just "fix itself" for this release :D. If not, I'll keep investigating (specifically, the double "Azure Pipelines Language Server" output looks suspicious). |
After the update to extension 1.249.0, the problem persists. I believe I've been experiencing this error for quite some time — in fact, ever since #583 was resolved. That is at least consistent with there having been no work in that area for the current release. The error message now is slightly different: Initially, there was no duplicate Azure Pipelines Language output channel after updating the extension. However, I was able to recreate the duplicate channel:
|
FWIW, I polled six colleagues at work, and all six were able to reproduce the issue. We reproduced the issue on both Windows and macOS using both company-provided and personal machines. |
Wow, interesting, okay. I'll dig deeper into this and see if I can add any logging that will help. Thank you for the detailed analysis! |
Aha! I have a repro. Do you by any chance have a workspace folder open in VS Code? Or are you trying to open a file directly? (aka, does I believe this was caused by this change: microsoft/azure-pipelines-language-server@1e8432b#diff-6ca8c5115f7d741691ab47c62cd9f0dedf4a4dd5cd137a264427c58da9ff9e51R90 Though I wonder why we didn't get any reports on 1.237.0 which is when that change was released. |
At least in my case, I might not have edited any pipelines at that time. More generally, I suspect a lot of us users had the initial reaction of hoping the problem self-resolves or gets reported by someone else. |
Excellent, thanks. Since we have a workaround now, I'll target a fix for this in January to give some extra time for the current release to bake and to avoid the possibility of something going wrong with a holiday release. I should also say this exposes a gap in our tests - all of them currently open a folder :P. |
Thanks for your attention on this! |
WORKAROUND
If you are experiencing this, try opening a folder first, then open the Azure Pipelines file you want to view.
Experiencing failure on YAML load. I am signed in with my @microsoft account. I have tried uninstalling, quit and restart but that has not helped.
Version: 1.94.2
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z (2 wks ago)
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
Azure Pipelines plugin 1.247.2
The text was updated successfully, but these errors were encountered: