Vscode-powershell: Wrong (closed) script was run in the debugger

Created on 23 Dec 2016  Â·  6Comments  Â·  Source: PowerShell/vscode-powershell

Please fill in these details so that we can help you!

System Details

  • Operating system name and version:
  • VS Code version:
  • PowerShell extension version:
  • Output from $PSVersionTable:
Evaluate $PSVersionTable in PowerShell and paste the output here

Issue Description

I am experiencing a problem with...

Attached Logs

Follow the instructions in the README
about capturing and sending logs.

Issue-Bug Needs-Repro-Info

Most helpful comment

No, it has not happened again, thanks.
On Tue, Jul 31, 2018 at 3:31 PM Tyler James Leonhardt <
[email protected]> wrote:

This is a pretty old issue. Can you still reproduce this issue?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/PowerShell/vscode-powershell/issues/415#issuecomment-409374666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6tVDlauxAyyyudeSrxlF6XKhO-jHi3ks5uMMy3gaJpZM4LU9DF
.

>

Scott Saari
Mobile: (602) 230-7824

All 6 comments

Hey @ssaari, can you provide some more context about this issue? Which script was run? When did it happen? Can you tell me the set of steps you took before the issue occurred?

I'm terribly sorry I probably don't know enough details to be helpful. The
script that ran unexpectedly had been open and run to debug on a previous
day, probably one day before. I remember opening a folder and having two
other scripts open from having been open before. One of them was run to
debug and that is when the output of the closed script started appearing in
the debug pane. This script was kicking off a secondary executable that
would have been bad to run at that time, so I closed everything out. I
haven't opened VS Studio since. I might be able to get those logs for
you. It's been really busy or I would have already, apologies once more.

On Fri, Dec 23, 2016 at 10:17 AM David Wilson notifications@github.com
wrote:

Hey @ssaari https://github.com/ssaari, can you provide some more
context about this issue? Which script was run? When did it happen? Can you
tell me the set of steps you took before the issue occurred?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/PowerShell/vscode-powershell/issues/415#issuecomment-269020208,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6tVKeE7tBLzmxKtlXeNB3YmBGYi8eZks5rLAIogaJpZM4LU9DF
.

>

Scott Saari

No problem Scott! If you get a chance to grab those logs I'd be happy to take a look. I've never heard of the wrong script being executed from VS Code's debugger before but there are a couple things I could look into there.

I have attached my logs. The script that ran by mistake was call run-refresh.3e.ps1 if that helps.
ssaari_logs.zip

This is a pretty old issue. Can you still reproduce this issue?

No, it has not happened again, thanks.
On Tue, Jul 31, 2018 at 3:31 PM Tyler James Leonhardt <
[email protected]> wrote:

This is a pretty old issue. Can you still reproduce this issue?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/PowerShell/vscode-powershell/issues/415#issuecomment-409374666,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AD6tVDlauxAyyyudeSrxlF6XKhO-jHi3ks5uMMy3gaJpZM4LU9DF
.

>

Scott Saari
Mobile: (602) 230-7824

Was this page helpful?
0 / 5 - 0 ratings