-
Notifications
You must be signed in to change notification settings - Fork 29.9k
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
Broken Debug Console #108202
Comments
From b8e87aa |
Actually it is easy to repro with the "VS Code" launch config. I guess I'm not sure what determines whether the debug console is shown or not when debugging starts because it is not shown for those configs. |
But I don't understand why the debug console is not opened for me when I start this config.
And when the debug console does not open early and get a chance to initialize itself, that's when this bug is triggered. |
It looks like @isidorn is out, so going ahead with a fix. Decided to just revert the fix for #107860 I think the right fix would be to figure out what the current session is without looking at the tree, which I think is possible but I'll leave that for @isidorn. Or, create the tree earlier. Then broke out the question of why the debug console doesn't appear when maybe it should, which makes this much easier to repro, into a separate issue. |
Simplest repro steps
|
@JacksonKearl did you verify when you approved? If not I can verify this issue |
It will need to be verified but the build is not released yet |
Now it is |
@roblourens thanks for jumping on this and for finding the root cause. |
"internalConsoleOptions": "neverOpen"
or a launch config that fails to start/attach so that the debug console is never openedGet a notification for this error
Hit the error in the debugger:
Seems that if the "select repl" action is valid at the time the viewPaneContainer is being created for the debug console, then it will invoke the actionViewItemProvider which assumes the tree has been instantiated already, but it hasn't yet, and it throws.
The text was updated successfully, but these errors were encountered: