There is no response for initialization / LSP takes too long to load on window using named pipes

[TheLeoP]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest version
• Search the existing issues.

Steps to reproduce

1. Start the LSP (on windows) using the following command pwsh "-NoProfile" "-NonInteractive" "C:/Users/pcx/AppData/Local/nvim-data/mason/packages/powershell-editor-services/PowerShellEditorServices/Start-EditorServices.ps1" "-HostName" "nvim" "-HostProfileId" "0" "-HostVersion" "1.0.0" "-LogPath" "C:\\Users\\pcx\\AppData\\Local\\Temp\\nvim/powershell_es.log" "-LogLevel" "Diagnostic" "-BundledModulesPath" "C:/Users/pcx/AppData/Local/nvim-data/mason/packages/powershell-editor-services" "-EnableConsoleRepl" "-SessionDetailsPath" "C:\\Users\\pcx\\Desktop/powershell_es.session.json" "-AdditionalModules" "@()" "-FeatureFlags" "@()"
2. Try to connect to it using named pipes (right now I'm only using a toy example)

Expected behavior

The LSP should work just like it does via STDIO.

Actual behavior

The LSP does not answer the initialization request or it takes too long to start (so the request comes too soon?). This is a very similimar (at least from the user point of view, I have no idea about this LSP internals) to #2092.

Error details

This is the log of powershell editor services. Like in #2092, it takes almost 2 minutes to load everything (does this even have an impact?), but this time there it doesn't seem to be trying to load the use profile.

powershell_es.log

(I'm sending enableProfileLoading: false in the initialization options, but I'm not sure if using named pipes instead of stdio changes something regarding this).

Environment data

Name                           Value
----                           -----
PSVersion                      7.3.9
PSEdition                      Core
GitCommitId                    7.3.9
OS                             Microsoft Windows 10.0.19045
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

3.14

Visuals

powershell_es.log

Maybe related to #2092 (?)

For context, I'm trying to create a Neovim plugin to use both the integrated terminal and the powershell debugger, but I'm having troubles even trying to connect to the language server using named pipes.