Bundled command-line tools hang after first character during interactive conflict resolution

[c.hol...@neurotronics.com]

I am using Windows 10 64-bit Enterprise, with the April 2018 update (1803). When using the command-line tools bundled with TortoiseSVN 1.10.0 64-bit, if there is a conflict, the conflict resolution prompt is displayed, but after the first character is typed (and echoed), svn.exe stops responding to input. It won't accept any other characters, Enter, or Ctrl-C. It has to be force killed in Task Manager.

I tried another Windows build of the Subversion tools (SlikSVN) and it doesn't have this issue in the same environment.

[Stefan]

Can reproduce the problem. But I haven't figured out why this happens yet:

for some reason, the _getch() API call returns always zero after every key typed. E.g. if you type 'q', then 'q' and '\0' is returned instead of just 'q'.

That's why it gets stuck in an endless loop (_getch() returning zero should only happen for function and cursor keys according to the docs).

So it might take me a while to figure this out...

Stefan

[Niemann, Hartmut]

Perhaps it is thinking UTF16 and returning ‘q’ encoded in 16 bits?

I saw strange things with windows wide chars ... :-)

 

Mit freundlichen Grüßen
Dr. Hartmut Niemann

Siemens AG
Mobility Division
Rolling Stock
Standardization, Remote Control, Display
MO RS LM EN CCI SRD
Werner-von-Siemens-Str. 67
91052 Erlangen, Deutschland
Mobil: +49 173 5342327
mailto:hartmut...@siemens.com
www.siemens.com/ingenuityforlife

--
You received this message because you are subscribed to the Google Groups "TortoiseSVN" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/107d993e-47e0-4c03-84ed-81d98ba437ec%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[c.hol...@neurotronics.com]

This seems to be a UCRT bug:

https://developercommunity.visualstudio.com/content/problem/245451/unbuffered-console-io-is-broken-only-in-release-bu.html

[Stefan]

On Friday, May 25, 2018 at 3:26:22 PM UTC+2, (unknown) wrote:

This seems to be a UCRT bug:

https://developercommunity.visualstudio.com/content/problem/245451/unbuffered-console-io-is-broken-only-in-release-bu.html

Yes! That's exactly the problem.

Only I get the same problem in debug builds as well.

Seems we have to wait for MS to fix this...

Stefan

[dirk.umb...@googlemail.com]

Am Dienstag, 22. Mai 2018 22:04:45 UTC+2 schrieb (unbekannt):
> I am using Windows 10 64-bit Enterprise, with the April 2018 update (1803). When using the command-line tools bundled with TortoiseSVN 1.10.0 64-bit, if there is a conflict, the conflict resolution prompt is displayed, but after the first character is typed (and echoed), svn.exe stops responding to input. It won't accept any other characters, Enter, or Ctrl-C. It has to be force killed in Task Manager.
>
> I tried another Windows build of the Subversion tools (SlikSVN) and it doesn't have this issue in the same environment.

I'm clear about the solution. Is there something to do on Tortoise client side after Microsoft has fixed the bug? Do I have to install an update for Visual Studio 2017 on my PC to get that fix?

Thanks!

Dirk

[Stefan]

you need to wait for the next release.

I've also asked Ian to update VS on the nightly build server so once that's done you can use a nightly build.

Stefan

[david.a....@gmail.com]

Hey,

Sorry for being random but I have this issue at my work place. Have even tried the nightly but but still hangs when I try to resolve a conflict in SVN.exe.

Any advice?

Thanks