Kevin Lin

Thanks for the report - this seems to be an issue with insiders. Looking into what we can do about it on our side

This looks like a regression on the latest build of vscode-insider. submitted https://github.com/microsoft/vscode/issues/154886 and will wait on updates

meanwhile, adding a workaround that will be live with the v103 release tomorrow!

if you would like to have this working ahead of time, you can downgrade to 1.69.0 of insider by following instructions in https://stackoverflow.com/questions/69576354/is-it-possible-to-downgrade-vscode-insiders-download-older-insider-builds

will keep this open until it is resolved. it looks like vscode team is aware of this and working on a fix

thanks for the issue. was able to reproduce and launched a fix. should be live in a few minutes as 0.107.2

this has been fixed in v105.0

@Harshita-mindfire no rush - can you ping me when this is ready to re-review with the sub-grouped configs?

clean up old prs

thanks for this - can repro. we will work on a fix