search

JohnstonCode / svn-scm

SVN support for VS Code
MIT License
207 stars 87 forks source link

SVN+SSH again (Windows with TortoiseSVN) #927

Open GitMensch opened 4 years ago

GitMensch commented 4 years ago

Issue

Extension not working with svn+ssh//user@server/url using pageant keyring.

Steps to Reproduce

  1. checkout via TSVN using the https-schema
  2. Open Folder in vscode -> extension works, everything is shown
  3. checkout via TSVN using the url-schema above
  4. Open Folder in vscode -> extension seems to do nothing

SVN Output

Using svn "1.9.7" from "C:\Program Files\TortoiseSVN\bin\svn.exe"
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn cat src\TEST.src
[playground]$ svn info --xml
[playground]$ svn stat --xml --no-ignore --ignore-externals --show-updates
[playground]$ svn log -r1:HEAD --stop-on-copy --xml --with-all-revprops --verbose
[playground]$ svn log -r HEAD:1 --limit=50 --xml -v svn+ssh://me@server/opt/svn/svnroot/playground/trunk/src/TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn info --xml c:\dev\playground\src\TEST.src
[playground]$ svn cat src\TEST.src
[playground]$ svn log -r HEAD:1 --limit=50 --xml -v svn+ssh://me@server/opt/svn/svnroot/playground/trunk/@

Note: when using these exact commands from cmd.exe I see a reasonable file (cat), and the changeinfo in xml format and the log. Similar issue with the SVN Gutter extension (in this case standing on "Blamer started" in the status bar).

Screenshots

Still seen after waiting 6 minutes: grafik

GitMensch commented 8 months ago

While not having checked recently - does the svn+ssh protocol now work (then the state closed-not-planned is wrong)? If not: is it explicit expected to not work (in which case the README should note that)?

Or does that still needs investigation per your 2020 plan?

JohnstonCode commented 8 months ago

https://github.com/JohnstonCode/svn-scm/issues/1623

GitMensch commented 8 months ago

Can I suggest to reopen it and adding a label like "help-needed" or "needs-a-PR" or similar?

JohnstonCode commented 8 months ago

I think that is reasonable but it wont live indefinitely if there are no takers.