subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Hett <>
Subject Re: Problem with locking multiple files.
Date Mon, 09 May 2016 09:05:05 GMT
On 5/9/2016 10:55 AM, Stefan Hett wrote:
> On 5/9/2016 10:09 AM, Ivan Zhakov wrote:
>> On 6 May 2016 at 14:37, Stefan Hett<>  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.
> I'll forward that to the user on the TSVN list, since I don't have any 
> environment at hand here to reproduce the described issue.
Seems like I'm not fully awake yet... As far as I understood the issue, 
there's no way to reproduce the scenario just using the command line 
client, since that doesn't allow to lock multiple files over different 
paths (aka: there's no recursive-flag for svn lock).

The only way to reproduce the problem atm seems to be using some other 
client. In this particular case the issue is reported to be reproducible 
using TSVN 1.9.4 (which according to Stefan K√ľng uses the SVN API 
directly for the lock/unlock feature --- aka: I assume he's calling 
svn_ra_lock() by passing multiple path_revs - didn't check that, so take 
it with care).

Do you have a lead for me how to get any further information from the 
user which would help to investigate the issue? Since I don't have an 
environment at hand here, I can't try to reproduce the described 
scenario myself.

Stefan Hett

View raw message