There is already a debug configuration "PowerShell Launch Current File..."

[PrzemyslawKlys]

System Details

code -v1.27.2f46c4c469d6e6d8c46f268d1553c5dc4b475840fx64openssl config failed: error:02001003:system library:fopen:No such processPS C:\Users\pklys\OneDrive - Evotec\Support\GitHub\PSWinDocumentation\Ignore> $pseditor.EditorServicesVersion

Major  Minor  Build  Revision
-----  -----  -----  --------
1      8      4      0


PS C:\Users\pklys\OneDrive - Evotec\Support\GitHub\PSWinDocumentation\Ignore> code --list-extensions --show-versions
[createInstance] extensionManagementService depends on downloadService which is NOT registered.
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
openssl config failed: error:02001003:system library:fopen:No such process
PS C:\Users\pklys\OneDrive - Evotec\Support\GitHub\PSWinDocumentation\Ignore> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      5.1.17754.1
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.17754.1
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

I am experiencing a problem with... VSCode executing debug session that is invisible, unkillable and shows up for no reason. It's like I press F5 it doesn't register this and goes into hidden session/agenda outside of main powershell.

I do have logs from this but I don't think it contains anything worth while (nothing out of ordinary or crashing). If you want them I can send them over. it's 30mb file thou as I had that VSCode open for a while.

It's something I experience quite frequently. It's usually no problem but requires me to kill my powershell session. And even then like in this case it's not 100%. I just killed all my powershell sessions within this VSCode and restarted and F5 stays silent. I then went ahead and closed VSCode instance and restarted project. It loaded back but any F5 does this

I do have 4 other VSCode open thou. So I rerun some other script in other VSCode window and it finally unlocks and works again.

I've just been running for the last 5 hours a script that was loading data from Office 365/Azure into $Data / $DataExchange. Fortunately I did Export-CliXml on those variables (as I've been playing with ability to run some of my scripts remotely and then importing variables back) so I can Import-CliXML on that data. But that was a bit incidental. Otherwise I would lost "data". Not that it matters or that you have to worry about, just saying how impactful can it be.

[rjmholt]

I have a feeling this might be the same bug:
#1494

[PrzemyslawKlys]

Maybe, hopefully! Because at least there's something to go on. In my case it's just recording. Although in my case I didn't notice any crashing, I don't use breakpoints either. Just 'no debugging session' all the time. Over and over and over.

[PrzemyslawKlys]

1538906053-57222cd8-f5e5-4aaa-a3b1-223bd4cf84881538905813133.zip

I just had this case again.

10/7/2018 12:19:44 PM [VERBOSE] - Document formatting finished in 0.125s
10/7/2018 12:20:04 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:20:04 PM [VERBOSE] - Document formatting finished in 0.123s
10/7/2018 12:20:24 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:20:24 PM [VERBOSE] - Document formatting finished in 0.13s
10/7/2018 12:20:36 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:20:36 PM [VERBOSE] - Document formatting finished in 0.118s
10/7/2018 12:20:48 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:20:48 PM [VERBOSE] - Document formatting finished in 0.109s
10/7/2018 12:21:59 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:21:59 PM [VERBOSE] - Document formatting finished in 0.073s
10/7/2018 12:22:16 PM [VERBOSE] - Formatting entire document - file:///c%3A/Users/pklys/OneDrive%20-%20Evotec/Support/GitHub/PSWinDocumentation/Examples/test.ps1...
10/7/2018 12:22:20 PM [VERBOSE] - Document formatting finished in 3.491s

Notice how the last formatting takes 3 seconds even thou nothing has really changed. I believe it may be related to Formatting on Save and me trying to execute script at the same time. Can be related to #1562 where when script is running nothing else works.

It looks to me it could be kind of race condition where when the Formatting wins it locks out VSCode from running scripts. Scripts formatting continues to work.