JakubMisek, pre-release 1.58.17385 (out now - it may take a few minutes to appear in VSCode Extensions) addresses the issue.
We were unable to reproduce the issue, but according to provided logs, it should be fixed now :)
Please me us know, if it works now.