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

Re: Observed changes didn't match count

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Sat, 30 Oct 2010 00:11:45 +0200

Short version: it's a bug in Google's backend, and I can reproduce it
with neon but not with serf.

(more below)

Ryan Schmidt wrote on Fri, Oct 29, 2010 at 16:24:20 -0500:
> The Pure project is trying to switch from Subversion to Mercurial, and are having trouble with svnsync.
>
> http://groups.google.com/group/pure-lang/msg/bf588ebe14d6fb14
>
> On revision 2967, it gives the message "Observed changes didn't match count", and I get the same message when just doing an "svn log -v" on that revision:
>
> $ svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk
> svn: Observed changes didn't match count

[[[
% $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk --config-option servers:global:http-library=serf
------------------------------------------------------------------------
% echo $?
0
% $svn log -v -r2967 http://pure-lang.googlecode.com/svn/trunk --config-option servers:global:http-library=neon
...
subversion/libsvn_ra_neon/util.c:773: (apr_err=160004)
svn: Observed changes didn't match count
% echo %?
1
% ./tools/dev/which-error.py 160004
00160004 SVN_ERR_FS_CORRUPT
% $svn --version | head -n2
svn, version 1.7.0 (dev build)
   compiled Oct 27 2010, 15:38:01
%
]]]

> $
>
> "svn log" without "-v" works fine, as does "svn diff".
>
> Google searching for this error message yields only one other occurrence, which was not really solved.
>
> I'm unsure what we should try from here. Possibly this error is unique
> to Google Code's Subversion backend,

The error code confirms your suspicion. Furthermore, the word
"Observed" doesn't appear in Subversion's source code.

> but still I would have expected
> others to have run into it. Any suggestions?
>
>
>
Received on 2010-10-30 00:13:23 CEST

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

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