-
Notifications
You must be signed in to change notification settings - Fork 479
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
Debugging hangs when Import-Excel attempts to access an open file #2969
Comments
Thanks @sba923 for all the info... this looks like the stack trace:
Just to check, you dont have a profile which redefines out-default...correct? |
Nope, my profile doesn't redefine I think I can interact with about everything: the editor, menus, the Explorer/Search/Extensions.... panes, the debug console... basically anything except for the Terminal and the Run (debugging) pane. And I can close VS code using the top-right X ;-) |
This could be related to #2767 |
This issue was closed automatically as repro info was indicated as needed, but there has been no activity in over a week. Please feel free to reopen with any available information! |
Hey! There's been a lot of changes (for better or worse) to the extension since September, 2020. Please test the latest preview extension and re-open this if it still recurs! |
System Details
System Details Output
Issue Description
Take the following script:
If I run this script within VS Code, and Import-Excel fails because the file is open in Excel, I get:
and then VS Code hangs.
This occurs even if I set a breakpoint on the second line of the script.
Note: if the same script is run in a standard PowerShell 7.0.3 console, the script doesn't continue execution after the first line, but the user is returned to the PowerShell prompt:
Expected Behaviour
The error should be reported, and the script should continue (or the breakpoint at the second line should be hit)
Actual Behaviour
VS Code hangs. A restart is required.
Ctrl+C won't help because this will yield the same behavior as in #2713 (sort of endless prompt display).
Attached Logs
logs.zip
The text was updated successfully, but these errors were encountered: