You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a breakpoint on line 2 of the following file, and start the debugger.
importtimetime.sleep(5) # set a breakpoint on this lineprint('Nothing in particular')
When the debugger stops at the breakpoint, hit <leader>Dd to disconnect.
Expected Result
I should get a notification with the message disconnected.
Actual Result
No notification is raised, but I get [Process exited 0] in the DAP terminal.
The behaviour also depends on the sleep time. If I change the second line in the python file to time.sleep(0.1), the line Nothing in particular is printed to the DAP terminal before the process exit. I tried increasing the value of disconnect_timeout_sec in the adapter options, but this did not change the behaviour.
The text was updated successfully, but these errors were encountered:
That's up to the debug adapter. nvim-dap closes the connection after disconnect_timeout_sec to avoid waiting indefinitely. If the adapter doesn't send it there is nothing the client can do about it.
Debug adapter definition and debug configuration
Using the following minimal configuration for
nvim-dap
with thedebugpy
adapter, I cannot get thedisconnect
listener to work correctly.Debug adapter version
debugpy v1.8.1
Steps to Reproduce
Add a breakpoint on line 2 of the following file, and start the debugger.
When the debugger stops at the breakpoint, hit
<leader>Dd
to disconnect.Expected Result
I should get a notification with the message
disconnected
.Actual Result
No notification is raised, but I get
[Process exited 0]
in the DAP terminal.The behaviour also depends on the sleep time. If I change the second line in the python file to
time.sleep(0.1)
, the lineNothing in particular
is printed to the DAP terminal before the process exit. I tried increasing the value ofdisconnect_timeout_sec
in the adapter options, but this did not change the behaviour.The text was updated successfully, but these errors were encountered: