-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot Stop/Cancel Debugged Unit Tests #22605
Comments
Hello! Could you include a layout of your project and your logs from the |
Hi! Sure, here is the layout (note: it is reduced, i.e. a lot of files are removed) Click me
And here the logs Click me
Thank you in advance, @eleanorjboyd ! |
@paulacamargo25, could you jump in here? Seems like it might be a debugging / launch.json file issue. I am seeing the error |
@0xharold thanks for the detailed logs and project structure, very helpful! |
@eleanorjboyd Hi! Any update? :) |
@paulacamargo25, can you take a look? |
According to the error, it seems that the launch.json is wrong, could you send me your launch.json? |
Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off. |
@brettcannon @paulacamargo25 {
"version": "0.2.0",
"configurations": [
{
"args": [
"run",
"${file}"
// "--server.port",
// "SPECIFY_YOUR_OWN_PORT_NUMBER_HERE"
],
"module": "chainlit",
"name": "Python: Chainlit",
"request": "launch",
"type": "debugpy",
"justMyCode": false
},
{
// "args": ["--par", "from"],
"name": "Python: Current File",
"type": "debugpy",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal",
"justMyCode": false
}
]
} FYI: I have tried to use just "Python: Current File" (i.e. deleting the Chainlit one) and it seems it does not have an impact on it. My workspace might be really messed up though. For instance, In Testing section I can see two sets of tests: |
Thanks for your reply, according to your |
I would love to send these logs but now all works as expected, i.e. when I hit the stop button, the tests stop, the same applies for debugging. |
no worries! Glad it is working! If you experience this again feel free to comment on this issue with your logs. @haraslub are you still experiencing this issue and if so could you send your logs? Otherwise we will close this as resolved for now, thanks! |
Hi! Closing this as you are no longer experiencing it. Also the version of vscode coming out next week has some new updates which should help as I have fixed some edge cases around stop/cancel debugging |
Type: Bug
When I try to debug any unit test using Test Explorer, it always gets stuck. Tests don't hit the breakpoint, complete, or even stop when I click the Cancel Test Run button. I need to close VSC to terminate the test.
VS Code version: Code 1.84.2 (1a5daa3a0231a0fbba4f14db7ec463cf99d7768e, 2023-11-09T10:51:52.184Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Remote OS version: Linux x64 5.15.133.1-microsoft-standard-WSL2
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Extensions (67)
A/B Experiments
The text was updated successfully, but these errors were encountered: