On 6 May 2016 at 14:37, Stefan Hett <stefan_at_egosoft.com> wrote:
> Hi,
>
> this is in reference to a user reported problem on the TSVN mailing list [1]
>
> The user is having an issue with using TSVN 1.9.4 over a Java-SSL-Tunnel
> when trying to lock hundreds or thousands of files. The same operation works
> without problems when:
> - using TSVN 1.8.12 or
> - using the SVN command line client (1.8 or 1.9)
> - disabling the Java-SSL-Tunnel
>
> I've been pointed to issue #4557 [2] by stsp. I'm not 100% certain whether
> this really is the particular problem the user runs into but even if it
> wouldn't be the case here, the underlying issue of #4557 might be worth
> changing/fixing in 1.9 as well.
>
> The reasoning from a users / downstream-developer's point of view would be
> that the new way could fail in a particular environment which the old (aka:
> 1.8) way would work just fine. So if I as a developer make use of the new
> functionality, it would look like a regression to my userbase of my tool.
>
> Does that make sense to you? Should I create a new JIRA issue for that case
> (in contrast to SVN-4557 that would differ in that the effected version
> would be 1.9.x - not 1.8.x - aka: no regression)?
>
Could you please provide reproduction script using command line
client? As far I understand the problem in 'Java-SSL-Tunnel', not in
Subversion itself.
--
Ivan Zhakov
Received on 2016-05-09 10:09:38 CEST