`Comments (119)` + `There are no comments in this workspace yet.` after restarting extensions

[jsoref]

Type: Bug

1. Clone https://github.com/valkey-io/valkey
2. Open it in VS code
3. Switch to the GitHub Pull Requests sidebar
4. Expand the pull request Spelling valkey-io/valkey#2183 (for me it's in Created By Me, but you can use All Open or create a filter for this PR)
5. expand comments (it's a section that appears next to Terminal -- I don't precisely know how to do this)
6. use VSCode's extensions manager to restart extensions (I disabled a bunch of extensions and then restarted)
7. See Comments (119) + There are no comments in this workspace yet.

Extension version: 0.113.2025062009
VS Code version: Code 1.101.1 (Universal) (18e3a1e, 2025-06-18T13:35:12.605Z)
OS version: Darwin arm64 24.5.0
Modes:

System Info

Item	Value
CPUs	Apple M1 Max (10 x 2400)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on 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_graphite: enabled_on video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	24, 15, 12
Memory (System)	64.00GB (0.54GB free)
Process Argv	--crash-reporter-id 1fc67ee2-0174-4598-9f98-4537df0dd32c
Screen Reader	no
VM	0%

A/B Experiments

vspor879:30202332
vspor708:30202333
vspor363:30204092
binariesv615:30325510
c4g48928:30535728
962ge761:30959799
pythontbext0:30879054
cppperfnew:31000557
pythonrstrctxt:31112756
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31314491
996jf627:31283433
usemplatestapi:31297334
7bj51361:31289155
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003

[jsoref]

When I start browsing through, I end up having lost my comments and see something like this:

Essentially it had amnesia and I can slowly get the number back to 119 by manually visiting each file that has comments...

It's pretty painful:

I've apparently missed some...

Clicking the PR row itself yielded 122 comments...

This will lead me to my actual feature request (as opposed to this bug report)...

[alexr00]

To verify, you can use the GitHub Pull Request extension:

1. Don't check out a PR
2. From the Pull Requests view, open a PR diff which has comments
3. Restart extensions
4. Verify that the comment count in the Comments view matches the number of comments in the view.