v2.0.0-preview.6 fails with OmniSharp Error: System.InvalidOperationException: This operation is not supported for a relative URI.

[ant-druha]

Full trace is

2019-11-16 15:30:40.421 +03:00 [INF] highlight handler loaded
2019-11-16 15:30:40.472 +03:00 [DBG] Finding descriptor for initialize
2019-11-16 15:30:40.590 +03:00 [DBG] Starting: Routing Request (1) initialize
2019-11-16 15:30:40.598 +03:00 [DBG] Converting params for Request (1) initialize to OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams
2019-11-16 15:30:40.656 +03:00 [FTL] Failed to handle notification initialize
System.InvalidOperationException: This operation is not supported for a relative URI.
   at System.Uri.get_AbsolutePath()
   at OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams.get_RootPath()
   at Microsoft.PowerShell.EditorServices.Server.PsesLanguageServer.<>c.<<StartAsync>b__18_3>d.MoveNext() in D:\a\1\s\src\PowerShellEditorServices\Server\PsesLanguageServer.cs:line 114
--- End of stack trace from previous location where exception was thrown ---
   at OmniSharp.Extensions.LanguageServer.Server.LanguageServer.MediatR.IRequestHandler<OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeParams,OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult>.Handle(InitializeParams request, CancellationToken token)
   at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPostProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at MediatR.Pipeline.RequestPreProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
   at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.RouteRequest(TDescriptor descriptor, Request request, CancellationToken token)
2019-11-16 15:30:40.674 +03:00 [DBG] Finished: Routing Request (1) initialize in 77ms

EditorServices-IJ-2.log
Start-EditorServices-EditorServices-IJ-2.log

[TylerLeonhardt]

@ant-druha does Intelij offer the ability to see the payloads of the requests that are being sent to and from it via the language server protocol?

I get the feeling that the issue here is that that is sending a relative path for the "rootPath" property of the initialize request... where vscode always sends absolute paths.

@david-driscoll @mholo65 this is a solid reason for OmniSharp/csharp-language-server-protocol#181

[ant-druha]

The path is absolute. Attached the dump file.
protocol_messages_IJ.log

[TylerLeonhardt]

Thanks for the context @ant-druha and apologies for the issues here - it was a particularly large change that went into preview.6

Would you mind trying a build from master? I did make a change in the exact spot that threw the exception and am curious if the issue is already fixed.

[ant-druha]

Would you mind trying a build from master?

Sure @TylerLeonhardt Actually, could you advise how do I release the build package to try? Thanks.