Debug locks up on next run if you stop it before completing.

[ericHanson13]

Describe the bug If I run Debug and stop it before the process completes, then I run debug again it starts but then gets stuck. I have to stop it then start again to get it to run.

To Reproduce Steps to reproduce the behavior:

1. Have a breakpoint
2. Run Debug
3. At breakpoint, stop the debug session
4. Run the debug session again

Expected behavior Second debug session should continue without failing.

Versions:

• OS: Mac 12.5
• Robot Framework Version: 11.3.0
• Robot Framework Language Server Version: 0.49.0
• Client Version: Version: 1.70.0 (Universal) Commit: da76f93349a72022ca4670c1b84860304616aaa2 Date: 2022-08-04T04:38:55.829Z Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: 10.0.139.17-electron.0 OS: Darwin x64 21.6.0

"Worked" are from the session I let the debug session complete till the end. The others are from me stopping the debug at a breakpoint then trying to run it again. worked.dap.53512.log worked.pydevd.53527.log worked.robot.53527.log filename.dap.54590.log filename.dap.54764.log filename.pydevd.54604.log filename.robot.54604.log

[ericHanson13]

BTW It also does it running a bot using

• rpaframework==15.1.3 # https://rpaframework.org/releasenotes.html
• robotframework-faker==5.0.0

[cmin764]

@ericRobocorp Can you give it a try with the latest library 15.6.0 to see if somehow the unexpected behaviour miraculously disappears?

[ericHanson13]

That didn't work either. If I let it sit it will eventually say "Debug adapter timed out waiting for process event." and ask me to open the "launch.json" which I have copied here: { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "robotframework-lsp", "name": "Robot Framework: Launch .robot file", "request": "launch", "cwd": "^\"\\${workspaceFolder}\"", "target": "^\"\\${file}\"", "terminal": "integrated", "env": {}, "args": [] } ] }

[fabioz]

Closing this since the issue is that VSCode itself is not doing the new launch (my guess is that this is happening due to some leftover process -- discussing on slack).

[tantian1498]

那也没用。如果我保持静置，它最终会显示“调试等待进程事件超时”。并要求我打开我在此处复制的“launch.json”： { // Use IntelliSense to learn about possible attributes. // Hover to view descriptions of existing attributes. // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "robotframework-lsp", "name": "Robot Framework: Launch .robot file", "request": "launch", "cwd": "^\"\\${workspaceFolder}\"", "target": "^\"\\${file}\"", "terminal": "integrated", "env": {}, "args": [] } ] }

same problem, do you sovle it now?