Not sure where this bug should live. Language Server Bug

[bobbytreed]

Type: Bug

2022-09-20 17:19:56.996 -04:00 [DBG] Starting: Processing notification textDocument/didOpen
2022-09-20 17:19:56.996 -04:00 [DBG] Starting: Processing notification textDocument/didOpen
2022-09-20 17:19:56.996 -04:00 [DBG] Starting: Routing Notification textDocument/didOpen
2022-09-20 17:19:56.996 -04:00 [DBG] Starting: Routing Notification textDocument/didOpen
2022-09-20 17:19:56.996 -04:00 [VRB] Converting params for Notification textDocument/didOpen to OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams
2022-09-20 17:19:56.997 -04:00 [VRB] Converting params for Notification textDocument/didOpen to OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams
2022-09-20 17:24:57.011 -04:00 [VRB] Notification was cancelled due to timeout
2022-09-20 17:24:57.011 -04:00 [VRB] Notification was cancelled due to timeout

So basically, after a recent VS Code Update, it tries to convert the params and waits 5 minutes then finally cancels. What the user sees is the extension loading and then it sits there for 5 minutes. After the initial delay everything works as expected

VS Code version: Code - Insiders 1.72.0-insider (0dce868b85978716d4fc7bc48b6a6a54c6a39fd0, 2022-09-09T05:17:41.485Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: Yes

System Info

Item	Value
CPUs	Intel(R) Core(TM) i9-9900X CPU @ 3.50GHz (20 x 3504)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: disabled_off
Load (avg)	undefined
Memory (System)	127.71GB (68.35GB free)
Process Argv	--crash-reporter-id 12cb6401-d44d-49aa-8b89-b8e70fef5929
Screen Reader	no
VM	0%

Extensions (6)

Extension	Author (truncated)	Version
vscode-eslint	dba	2.2.6
prettier-vscode	esb	9.8.0
vscode-dotnet-runtime	ms-	1.5.0
powershell	ms-	2022.8.5
powershell-preview	ms-	2022.8.5
docindex	Tea	0.0.44

A/B Experiments

vsliv695:30137379
vsins829:30139715
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256198
vslsvsres303:30308271
pythonvspyl392:30422396
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805:30301674
bridge0708:30335490
bridge0723:30353136
cmake_vspar411cf:30557515
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vscaac:30438845
vsclangdf:30492506
c4g48928:30535728
dsvsc012cf:30540253
pylantcb52:30568093
vscccc:30564267
pyindex848:30568094

[bobbytreed]

OmniSharp has not updated their library today, and in normal VS Code the issue is resolved after the first delay and in insiders the issue is still there after the first delay.

This is what the conversation usually looks like with the server

2022-09-20 17:47:58.461 -04:00 [DBG] Starting: Processing notification textDocument/didOpen
2022-09-20 17:47:58.461 -04:00 [DBG] Starting: Processing notification textDocument/didOpen
2022-09-20 17:47:58.461 -04:00 [DBG] Starting: Routing Notification textDocument/didOpen
2022-09-20 17:47:58.461 -04:00 [DBG] Starting: Routing Notification textDocument/didOpen
2022-09-20 17:47:58.461 -04:00 [VRB] Converting params for Notification textDocument/didOpen to OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams
2022-09-20 17:47:58.461 -04:00 [VRB] Converting params for Notification textDocument/didOpen to OmniSharp.Extensions.LanguageServer.Protocol.Models.DidOpenTextDocumentParams
2022-09-20 17:47:58.473 -04:00 [DBG] Finding descriptors for textDocument/codeAction
2022-09-20 17:47:58.473 -04:00 [DBG] Finding descriptors for textDocument/codeAction
2022-09-20 17:47:58.474 -04:00 [VRB] Found attributes 1, ["markdown::file:///d:/PullRequest%20Repos/MicrosoftDocs/azure-docs-pr/articles/data-factory/concepts-data-flow-column-pattern.md"]
2022-09-20 17:47:58.474 -04:00 [VRB] Found attributes 1, ["markdown::file:///d:/PullRequest%20Repos/MicrosoftDocs/azure-docs-pr/articles/data-factory/concepts-data-flow-column-pattern.md"]
2022-09-20 17:47:58.474 -04:00 [VRB] Looking for handler for descriptors textDocument/codeAction
2022-09-20 17:47:58.474 -04:00 [VRB] Looking for handler for descriptors textDocument/codeAction
2022-09-20 17:47:58.474 -04:00 [VRB] Checking handler textDocument/codeAction:DocIndex.VsCode.Server.CodeActionHandler
2022-09-20 17:47:58.474 -04:00 [VRB] Checking handler textDocument/codeAction:DocIndex.VsCode.Server.CodeActionHandler
2022-09-20 17:47:58.474 -04:00 [VRB] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.CodeActionRegistrationOptions
2022-09-20 17:47:58.474 -04:00 [VRB] Registration options OmniSharp.Extensions.LanguageServer.Protocol.Models.CodeActionRegistrationOptions
2022-09-20 17:47:58.474 -04:00 [VRB] Document Selector [/*.md], [/.yml]
2022-09-20 17:47:58.474 -04:00 [VRB] Document Selector [**/.md], [**/*.yml]
2022-09-20 17:47:58.474 -04:00 [DBG] Finished: Routing Notification textDocument/didOpen in 12ms
2022-09-20 17:47:58.474 -04:00 [DBG] Finished: Routing Notification textDocument/didOpen in 12ms
2022-09-20 17:47:58.474 -04:00 [DBG] Finished: Processing notification textDocument/didOpen in 12ms
2022-09-20 17:47:58.474 -04:00 [DBG] Finished: Processing notification textDocument/didOpen in 12ms

So most likely something changed in the payload of the textDocument/didOpen possibly?

[bobbytreed]

I should mention as well that the only recent change to my code base did not cause this issue as it was working fine for me and a colleague until we both got a vs code update, then the issue started.