F2 stopped working properly after recent update

[Avivhdr]

• VSCode Version: 1.40.0 (user setup)
• OS Version: Microsoft Windows 10 Enterprise

Steps to Reproduce:

1. Putting the cursor on a variable inside a function
2. pressing F2
3. Renaming the variable in the input that apears.
4. Pressing Enter.

Expected results:

1. All appearances of the variable in the scoop will be renamed
2. No error should appear.
3. I could preform the same action again (on the same variable or on another one).

Actual Results:

1. All appearances of the variable in the scoop were renamed.
2. I got the following error message:
   
3. When trying F2 for the second time i got the following message and the input in which i should enter the new name didn't appear:
   (I was pressing F2 when the cursor was on "channel_index") :
   .

Does this issue occur when all extensions are disabled?:
No, when the extension is disabled, pressing F2 doesn't trigger any reaction.

The extension is called "TypeScript and JavaScript Language Features".
The error indicates a TypeScript issue.
I don't use typescript at all so i do not need it's features.

Restarting vscode and disabling & enabling the extension didn't help,

Thanks a lot!

[mjbvz]

Can you please share the TS Server log so we understand why the server restarts in the first place:

1. Set "typescript.tsserver.log": "verbose",
2. Restart VS Code and reproduce the problem
3. Back in VS Code, go to the TypeScript section of output panel
4. At the very top of this output, there should be a line that prints the path to the main server log. It look like this (note the <semantic> part) :

[Info  - 4:06:59 PM] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20191111T144045/exthost1/vscode.typescript-language-features/tsserver-log-F2rDlk/tsserver.log

Please look through that log file for errors or stack traces (they should be near the bottom). If you can share the log, I can also take a look to see if anything stands out

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

[vscodebot]

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.

Happy Coding!

[mjbvz]

Closing as more information is needed to investigate

Please test using the latest VS code insiders build (with TypeScript 3.7.2+)