On Mon, Mar 19, 2012 at 5:24 PM, Greg Stein <gstein_at_gmail.com> wrote:
> On Mon, Mar 19, 2012 at 18:16, Greg Stein <gstein_at_gmail.com> wrote:
>> On Mon, Mar 19, 2012 at 16:48, Hyrum K Wright <hyrum.wright_at_wandisco.com> wrote:
>>> [ warning: investigation is still ongoing, but I thought I'd report this here.]
>>> I'm trying to debug the Ev2 shims over ra_dav. In doing so, I've
>>> discovered an inconsistency between ra_serf and ra_neon (surprise!)
>> ra_neon uses a "replay-report" while ra_serf uses an "update-report".
>> The former provides the rev= attribute.
>> I don't know why Neon uses the replay-report instead of the
>> update-report. I dunno what the differences are.
> What operations are you using? And why is it different between the two RA runs?
I see this on history test 1 (among others) when running davautocheck
and compiled with the shims enabled. It happens run running 'svn up
-r1' when the working copy is at r2, and r2 had a file replacement.
I might have been wrong about which bit of ra_neon was driving the
delete_entry() handler. I'll double check that bit later this
> Note: in neon/fetch.c:1845, I see that SVN_INVALID_REVNUM is passed to
> delete_entry(). That happens when ra_neon runs an update-report.
uberSVN: Apache Subversion Made Easy
Received on 2012-03-20 01:05:21 CET