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
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
debugpy version: lastest version
OS and version: MacOS Ventura 13.3
Python version (& distribution if applicable, e.g. Anaconda): 3.11 3.10 (basically all versions i tested with)
Using VS Code or Visual Studio: VS Code
Actual behavior
When debugging test in async written with combo of pytest and playwright, the command line isn't responsible for any actions performed by browser, it stuck afterward(deadlock). However using pdb debugger, it works but the problem is pdb debugger also doesn't have good UX and doesn't suuport async natively.
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
Actual behavior
When debugging test in async written with combo of pytest and playwright, the command line isn't responsible for any actions performed by browser, it stuck afterward(deadlock). However using pdb debugger, it works but the problem is pdb debugger also doesn't have good UX and doesn't suuport async natively.
Expected behavior
no deadlock when using terminal in debugging
Steps to reproduce:
The text was updated successfully, but these errors were encountered: