You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Blair Zajac <bl...@orcaware.com> on 2007/08/09 02:12:12 UTC
svnsync: REPORT request failed but sync continues
I'm syncing nine repositories from one office to another using the
Windows 1.4.4 client from a http:// to a file:/// repository, and I
got this on two different occasions:
Copied properties for revision 344.
Committed revision 345.
Copied properties for revision 3svnsync: REPORT request failed on
'http://hostname/svn/repos'
svnsync: REPORT of 'http://hostname/svn/repos': Could not read chunk
size: connection was closed by server. (http://pangosrc)
45.
Committed revision 346.
Copied properties for revision 346.
Committed revision 347.
Copied properties for revision 347.
Committed revision 348.
Copied properties for revision 348.
The concerning thing is that the message appeared but the sync
continued.
Is this something to worry about? Was the data successfully
transfered over completely? It looks like it was since no successive
commits failed.
However, to somebody who doesn't know, seeing these warnings doesn't
give warm-fuzzies that everything worked correctly.
If so, can we have have this message be silenced or give a message
saying it retried and worked?
Thanks,
Blair
--
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<bl...@orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnsync: REPORT request failed but sync continues
Posted by "C. Michael Pilato" <cm...@collab.net>.
Blair Zajac wrote:
> It would be nice if svnsync could resync all the revision properties,
> instead of having to sync each one by hand, as I don't have a list of
> revisions which gave an error, but it's not hard to script it either.
I changed svnsync in 1.5 so you could do exactly that:
usage: svnsync copy-revprops DEST_URL [REV[:REV2]]
And yes, you can use the keyword HEAD for one of the revisions.
--
C. Michael Pilato <cm...@collab.net>
CollabNet <> www.collab.net <> Distributed Development On Demand
Re: svnsync: REPORT request failed but sync continues
Posted by Blair Zajac <bl...@orcaware.com>.
On Aug 16, 2007, at 2:49 PM, Garrett Rooney wrote:
> On 8/8/07, Blair Zajac <bl...@orcaware.com> wrote:
>> I'm syncing nine repositories from one office to another using the
>> Windows 1.4.4 client from a http:// to a file:/// repository, and I
>> got this on two different occasions:
>>
>> Copied properties for revision 344.
>> Committed revision 345.
>> Copied properties for revision 3svnsync: REPORT request failed on
>> 'http://hostname/svn/repos'
>> svnsync: REPORT of 'http://hostname/svn/repos': Could not read chunk
>> size: connection was closed by server. (http://pangosrc)
>> 45.
>> Committed revision 346.
>> Copied properties for revision 346.
>> Committed revision 347.
>> Copied properties for revision 347.
>> Committed revision 348.
>> Copied properties for revision 348.
>>
>> The concerning thing is that the message appeared but the sync
>> continued.
>>
>> Is this something to worry about? Was the data successfully
>> transfered over completely? It looks like it was since no successive
>> commits failed.
>>
>> However, to somebody who doesn't know, seeing these warnings doesn't
>> give warm-fuzzies that everything worked correctly.
>>
>> If so, can we have have this message be silenced or give a message
>> saying it retried and worked?
>
> Since nobody replied and this is still sitting in my inbox...
>
> Yes, it seems like a problem in svnsync (something somewhere must be
> ignoring an error where it should be breaking out), but it seems
> likely that nothing has gone overly wrong with your repository. If a
> commit had really failed then the next commit would have errored out
> because the revision numbers would be out of sync (i.e. commit to sync
> revision N+1 would have resulted in the creation of revision N, which
> svnsync checks for). Worst case scenario as far as I can see is that
> maybe some revprops weren't copied over, in which case you can just
> recopy them manually with the copy-revprops command.
Thanks Garrett. Good to know that that check is in there.
It would be nice if svnsync could resync all the revision properties,
instead of having to sync each one by hand, as I don't have a list of
revisions which gave an error, but it's not hard to script it either.
Regards,
Blair
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: svnsync: REPORT request failed but sync continues
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
On 8/8/07, Blair Zajac <bl...@orcaware.com> wrote:
> I'm syncing nine repositories from one office to another using the
> Windows 1.4.4 client from a http:// to a file:/// repository, and I
> got this on two different occasions:
>
> Copied properties for revision 344.
> Committed revision 345.
> Copied properties for revision 3svnsync: REPORT request failed on
> 'http://hostname/svn/repos'
> svnsync: REPORT of 'http://hostname/svn/repos': Could not read chunk
> size: connection was closed by server. (http://pangosrc)
> 45.
> Committed revision 346.
> Copied properties for revision 346.
> Committed revision 347.
> Copied properties for revision 347.
> Committed revision 348.
> Copied properties for revision 348.
>
> The concerning thing is that the message appeared but the sync
> continued.
>
> Is this something to worry about? Was the data successfully
> transfered over completely? It looks like it was since no successive
> commits failed.
>
> However, to somebody who doesn't know, seeing these warnings doesn't
> give warm-fuzzies that everything worked correctly.
>
> If so, can we have have this message be silenced or give a message
> saying it retried and worked?
Since nobody replied and this is still sitting in my inbox...
Yes, it seems like a problem in svnsync (something somewhere must be
ignoring an error where it should be breaking out), but it seems
likely that nothing has gone overly wrong with your repository. If a
commit had really failed then the next commit would have errored out
because the revision numbers would be out of sync (i.e. commit to sync
revision N+1 would have resulted in the creation of revision N, which
svnsync checks for). Worst case scenario as far as I can see is that
maybe some revprops weren't copied over, in which case you can just
recopy them manually with the copy-revprops command.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org