Viewing HEAD information shows all information has changed and kills PowerShell extension

[mpearon]

• VSCode Version: 1.20.1
• OS Version: Windows 10 1607
• Extension Version: 1.19.0
• System Language: English

Issue

After a versioned file is modified (in this case a .psm1) and saved, the plugin detects changes. I then switch to Source Control in the Activity Bar. If I just submit the file, all is well - but if I click the file to view the HEAD info, it reports back that the entire file was changed, then after a moment, the PowerShell session terminates.

• If I view the HEAD in Tortoise, it correctly displays the change data.

Steps to Reproduce

• Modify versioned file
• View head information for modified file by clicking on filename in Changes pane.

Sample

[edgardmessias]

@mpearon , you can send the svn log?

[mpearon]

@edgardmessias - Sorry for the delay - back to work after a long weekend. I hope this is what you're after:

Using svn 1.9.7 (r1800392) from C:\Program Files\TortoiseSVN\bin\svn.exe
[DIT]$ svn info --xml
[DIT]$ svn stat --xml --no-ignore
[DIT]$ svn log -r BASE:HEAD -q --xml
[DIT]$ svn info --xml
[DIT]$ svn stat --xml --no-ignore
[DIT]$ svn stat --xml --no-ignore
[DIT]$ svn info --xml

That is when it is in the state you see in the screenshot above. Something to note, though: the PowerShell extension didn't bomb out this time.

[edgardmessias]

@mpearon, I can't reproduce here @JohnstonCode, you can reproduce?

[JohnstonCode]

@edgardmessias unable to reproduce here

[mpearon]

Is there anything more I can provide you guys for troubleshooting? It's consistent on my end. In the meantime, I'll verify that I can reproduce the issue on another machine with the same environment.

[JohnstonCode]

Yeah if you can try on another machine in the same environment that will help.

[edgardmessias]

@mpearon, try disable all plugins and run. Maybe it's another plugin the problem

[mpearon]

@edgardmessias and @JohnstonCode - I have switched to a new machine, synced my settings, then disabled all extensions. Unfortunately, this was all to no avail.

Here are a few screenshots Disabled settings:

Head from vsCode:

Head from Tortoise:

[JohnstonCode]

@mpearon Thanks for going through all that trouble.

I'll try again to replicate.

[JohnstonCode]

@mpearon can you screenshot the output window when you are getting HEAD from the screenshot above?

[mpearon]

@JohnstonCode - It's no problem at all! I greatly appreciate you taking the time to troubleshoot! :)

If this is what you're after (hopefully I didn't misunderstand), there isn't much to see:

Edit: This is the same with and without other extensions enabled.

[JohnstonCode]

Can you screenshot the debug console as well please?

[edgardmessias]

Not running the command: svn cat ....

[edgardmessias]

@mpearon, please, run the commands: svn info <filename> and svn status --no-ignore <filename>

[mpearon]

@JohnstonCode and @edgardmessias - Here is the output you requested.

svn info:

PS Microsoft.PowerShell.Core\FileSystem::\\SERVERNAME\DIT> svn info \\SERVERNAME\DIT\ScriptRepository\Modules\Modules\ServiceDesk\ServiceNow\CTS-ServiceNow.psm1
Path: ScriptRepository\Modules\Modules\ServiceDesk\ServiceNow\CTS-ServiceNow.psm1
Name: CTS-ServiceNow.psm1
Working Copy Root Path: \SERVERNAME\DIT
URL: https://SERVERNAME/svn/common/DIT/ScriptRepository/Modules/Modules/ServiceDesk/ServiceNow/CTS-ServiceNow.psm1
Relative URL: ^/DIT/ScriptRepository/Modules/Modules/ServiceDesk/ServiceNow/CTS-ServiceNow.psm1
Repository Root: https://SERVERNAME/svn/common
Repository UUID: 4bc623e6-e24c-4786-a4d0-aa7ffe565fda
Revision: 104
Node Kind: file
Schedule: normal
Last Changed Author: matthew_pearon
Last Changed Rev: 104
Last Changed Date: 2018-02-26 09:24:17 -0600 (Mon, 26 Feb 2018)
Text Last Updated: 2018-02-26 09:19:18 -0600 (Mon, 26 Feb 2018)
Checksum: 5f9354d73c311275ed80465f755592f2098bb4e3

svn status --no-ignore: M \\SERVERNAME\DIT\ScriptRepository\Modules\Modules\ServiceDesk\ServiceNow\CTS-ServiceNow.psm1

[edgardmessias]

lOl, UNC path, I can now do test

[mpearon]

I'm sorry! I didn't think to mention that it was a UNC path. After a few years in this field, you would think that my default posture would be to offer all details - even the ones I wouldn't think to be related/important.

[edgardmessias]

@mpearon, test this: https://ci.appveyor.com/api/buildjobs/5wgi9unbr9liw22p/artifacts/svn-scm.vsix

Instalation: https://code.visualstudio.com/docs/editor/extension-gallery#_install-from-a-vsix

[mpearon]

@edgardmessias - I was able to add the VSIX. For whatever reason, vsCode isn't getting the hint that it is acting as an SC provider.

Proof that it is installed:

[edgardmessias]

Sorry, I find a bug in package.

Try this: svn-scm.zip

[mpearon]

@edgardmessias - The installation procedure requested a couple of reloads that time, but vsCode is still not seeing the SC provider for some reason. Any logs I can provide you?

Edit - I tried this again, and it worked. Testing the Head issue now.

[mpearon]

@edgardmessias - Unfortunately, it looks the same:

This was the same with and without other extensions enabled.

[edgardmessias]

Disable the auto update and reinstall

[mpearon]

Oh, I didn't think about the auto-update getting it. Whatever you did there fixed the issue! :)

[edgardmessias]

Good, now wait the new release.

[mpearon]

Awesome! Thank you for all of your assistance and troubleshooting! :) Thank you too, @JohnstonCode!