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
when triggering a breakpoint in one thread (the desired breakpoint), other threads are displayed and editor jumps to those threads without having breakpoints at those locations.
Extension version (available under the Extensions sidebar): 2018.8.0 (04 September 2018)
OS and version: MacOS Sierra 10.12.6
Python version (& distribution if applicable, e.g. Anaconda): 3.7.1
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: Only package installed is vscode-python
Actual behavior
when triggering a breakpoint in one thread (the desired breakpoint), other threads are displayed and editor jumps to those threads without having breakpoints at those locations.
Expected behavior
The process breaks at the desired current file and line .
Steps to reproduce:
Set breakpoint after another process that presumably creates another thread, in this case start a mongodb connection
Start debug, app will hit breakpoint and immediately open another file and stope
Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
all are blank
Output from Console under the Developer Tools panel (toggle Developer Tools on under Help)
Occurs after process is continued and allowed to finish..
console.ts:136 [Extension Host] Python Extension: Error in debugger Banner Error: Missing required @injectable annotation in: Random.
at getTargets (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/planning/reflection_utils.js:20:15)
at Object.getDependencies (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/planning/reflection_utils.js:11:19)
at /Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/planning/planner.js:106:51
at Array.forEach (<anonymous>)
at _createSubRequests (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/planning/planner.js:94:20)
at Object.plan (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/planning/planner.js:129:9)
at /Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/container/container.js:316:37
at Container._get (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/container/container.js:309:44)
at Container.get (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/node_modules/inversify/lib/container/container.js:228:21)
at ServiceContainer.get (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/ioc/container.js:28:89)
at DebuggerBanner.<anonymous> (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:163:55)
at Generator.next (<anonymous>)
at /Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:18:71
at new Promise (<anonymous>)
at __awaiter (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:14:12)
at DebuggerBanner.getDebuggerLaunchThresholdCounter (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:158:16)
at DebuggerBanner.<anonymous> (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:135:22)
at Generator.next (<anonymous>)
at /Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:18:71
at new Promise (<anonymous>)
at __awaiter (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:14:12)
at DebuggerBanner.passedThreshold (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:133:16)
at DebuggerBanner.<anonymous> (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:72:30)
at Generator.next (<anonymous>)
at /Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:18:71
at new Promise (<anonymous>)
at __awaiter (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:14:12)
at DebuggerBanner.shouldShow (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:68:16)
at DebuggerBanner.<anonymous> (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:188:37)
at Generator.next (<anonymous>)
at fulfilled (/Users/currentuserfolder/.vscode/extensions/ms-python.python-2018.8.0/out/client/debugger/banner.js:15:58)
at <anonymous>
t.log @ console.ts:136
t._logExtensionHostMessage @ extensionHost.ts:412
(anonymous) @ extensionHost.ts:224
emitTwo @ events.js:126
emit @ events.js:214
emit @ internal/child_process.js:772
_combinedTickCallback @ internal/process/next_tick.js:141
_tickCallback @ internal/process/next_tick.js:180
The text was updated successfully, but these errors were encountered:
I started getting the same issue (running on Windows). As @egorse suggested, looking for the thread and proceeding from there seem to be okay so the issue could be related to some threading issue or order of breakpoints.
confirming the thread workaround above works for me, and downgrading the extension to the previous version to 2018.7.1 via vsix also addresses this problem. Will watch #2498 before updating...
when triggering a breakpoint in one thread (the desired breakpoint), other threads are displayed and editor jumps to those threads without having breakpoints at those locations.
Very similar to the bug reported here and closed
microsoft/vscode#58125
Environment data
Actual behavior
when triggering a breakpoint in one thread (the desired breakpoint), other threads are displayed and editor jumps to those threads without having breakpoints at those locations.
Expected behavior
The process breaks at the desired current file and line .
Steps to reproduce:
Set breakpoint after another process that presumably creates another thread, in this case start a mongodb connection
Start debug, app will hit breakpoint and immediately open another file and stope
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
)Occurs after process is continued and allowed to finish..
The text was updated successfully, but these errors were encountered: