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
After stepping in the train function the debugger should take you to the definition of the function
Actual behaviour
Does not step into the function. Does not debug the third party code.
Behaves like justMyCode is true
Steps to reproduce:
Create a sample test case with usage of third party library function
Discover Tests
Add a breakpoint inside the function defintion or exactly on the method call
Select the Debug: Tests launch config from the Debugging explorer
Debug the test using the Run Test | Debug Test menu that appears on each test
OR use the Python: Debug Test Method command
Step into function
Logs
Frame skipped from debugging during step-in.
Note: may have been skipped because of "justMyCode" option (default == true). Try setting "justMyCode": false in the debug configuration (e.g., launch.json).
Additional Details
Changing the launch.json to (adding the console option)
Environment data
python.languageServer
setting: 0.5.31.0Setup
launch.json
settings.json
Test Case
Expected behaviour
After stepping in the
train
function the debugger should take you to the definition of the functionActual behaviour
Does not step into the function. Does not debug the third party code.
Behaves like
justMyCode
istrue
Steps to reproduce:
Debug: Tests
launch config from the Debugging explorerRun Test | Debug Test
menu that appears on each testOR use the
Python: Debug Test Method
commandLogs
Additional Details
Changing the launch.json to (adding the console option)
The terminal outputs an error. The debug breakpoints do not trigger even for my own code
If you remove the
Debug: Tests
launch object the above issue disappers butjustMyCode
still doesn't change the behavior.The text was updated successfully, but these errors were encountered: