Cannot launch pytest debugger

[lramos15]

Testing #21495

I receive this error when trying to debug

2023-06-27 08:12:45.590 [error] Pytest test execution error
 TypeError: Cannot read properties of undefined (reading 'launchDebugger')
    at t.PytestTestExecutionAdapter.runTestsNew (/Users/lramos15/.vscode-insiders/extensions/ms-python.python-2023.11.11781018/out/client/extension.js:2:859042)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at t.PytestTestExecutionAdapter.runTests (/Users/lramos15/.vscode-insiders/extensions/ms-python.python-2023.11.11781018/out/client/extension.js:2:857588)
    at t.WorkspaceTestAdapter.executeTests (/Users/lramos15/.vscode-insiders/extensions/ms-python.python-2023.11.11781018/out/client/extension.js:2:879594)
    at async Promise.all (index 0)
    at D.runTests (/Users/lramos15/.vscode-insiders/extensions/ms-python.python-2023.11.11781018/out/client/extension.js:2:842000)
    at e.$A_b.k (/Applications/Visual Studio Code - Insiders.app/Contents/Resources/app/out/vs/workbench/api/node/extensionHostProcess.js:103:6852)
    at async Promise.all (index 0)

[rzhao271]

I encountered the same error, but I noticed after refreshing the tests or reloading the window that fewer test cases showed up? When I placed a breakpoint in one of the remaining test cases, I was able to debug it.
I tested the pytest TPI first, so maybe that picked up more test cases than were actually supported by unittest even when I reconfigured the tests to be run by unittest?

Edit: Got some repro steps.

1. Configure the tests to be run with pytest on the root directory .. All tests should show up.
2. Configure the tests to be run with unittest on the root directory . and only for test files of form test_*.py. 🐛 All tests still show up.
3. Refresh the tests. 🐛 All tests still show up.
4. Attempt to debug a test in test_two_classes.py. 🐛 The error above shows up.

[eleanorjboyd]

@karthiknadig, thoughts on this? When we talked last it seemed semi-impossible for this to happen but we continue to get reports on it.

[karthiknadig]

@eleanorjboyd We have to see if we can repro this. I can't really say what is going on. unless we are somehow setting it to undefined.

[eleanorjboyd]

@lramos15 do you remember the steps you took when you saw this error? Trying to find similarities with @rzhao271 comment as I have tried to repro this issue and have been unsuccessful in the past. Thanks

[lramos15]

@lramos15 do you remember the steps you took when you saw this error? Trying to find similarities with @rzhao271 comment as I have tried to repro this issue and have been unsuccessful in the past. Thanks

I just clicked the little debug icon next to the test in the test UI. Then it didn't work. I don't recall anything really special about it.

[michaelgonnella]

Hello, I'm running into the same issue while running from within a dev container in VS Code. VSCode is on version 1.81.1, and Python extension version v2023.14.0.

2023-08-23 13:53:31.022 [error] Pytest test execution error
 [TypeError: Cannot read properties of undefined (reading 'launchDebugger')
	at t.PytestTestExecutionAdapter.runTestsNew (/root/.vscode-server/extensions/ms-python.python-2023.14.0/out/client/extension.js:2:860683)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)
	at async t.PytestTestExecutionAdapter.runTests (/root/.vscode-server/extensions/ms-python.python-2023.14.0/out/client/extension.js:2:859184)
	at async t.WorkspaceTestAdapter.executeTests (/root/.vscode-server/extensions/ms-python.python-2023.14.0/out/client/extension.js:2:881277)
	at async Promise.all (index 0)
	at async D.runTests (/root/.vscode-server/extensions/ms-python.python-2023.14.0/out/client/extension.js:2:843548)
	at async C.k (/vscode/vscode-server/bin/linux-x64/6c3e3dba23e8fadc360aed75ce363ba185c49794/out/vs/workbench/api/node/extensionHostProcess.js:107:6002)
	at async Promise.all (index 0)]

[eleanorjboyd]

@connor4312 do you have any thoughts on this? We are using inversify to inject the debugLauncher into a control class which then handles creating the test adapters and calling run/discover on them. Not sure if you have seen a similar problem in core ever or if you do anything specific with the launchDebugger. Thanks

[connor4312]

While I do use inversify in js-debug, I'm not at all familiar with the internals of the python extension.

[michaelgonnella]

I actually was to able to (temporarily) get past this by uninstalling the Python extension from my running container, and then reinstalling the same version. Since then I have been able to debug.

[eleanorjboyd]

still unable to repro this issue so since it has been a month I am going to close this. Please comment if you are running into this issue and I can reopen. Thanks