heads up that we've found the issue and have released a fix in

0.107.1

(should be live in a few minutes - you might need to reload vscode to see the updated extension)