[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Catching dangling transactions

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2003-10-12 02:39:52 CEST

Philip Martin <philip@codematters.co.uk> writes:

> Philip Martin <philip@codematters.co.uk> writes:
>> Those two updates are not quite the same, after the first update fails
>> the working copy is marked incomplete. When I try it, all obstructed
>> updates in an incomplete working copy leave behind a transaction.
> I'm not really an expert in this bit of the code, but the error
> handling at the end of svn_repos_finish_report looks a bit suspect to
> me, if svn_repos_dir_delta returns an error the transactions are not
> removed.

After reading svn_repos.h, it appears to be the callers responsibilty.
In that case the problem is probably in svn_wc_crawl_revisions, all
those SVN_ERRs bypass the abort_report: processing, in this particuar
case the reporter->finish_report call is the culprit.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 12 02:41:10 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.