On Mon, 18 Apr 2011 13:51 +0300, "Daniel Shahaf" <d...@daniel.shahaf.name> wrote: > On Mon, 18 Apr 2011 16:05 +0530, "Arwin Arni" <ar...@collab.net> wrote: > > Hi All, > > > > This patch adds a test case to > > subversion/tests/cmdline/dav-mirror-autocheck.sh to showcase the > > following bug. > > > > In a master/slave repositories setup where writes are proxied to the > > master and reads are handles by the slave repository, if the slave > > repository is behind the master by one or more revisions, certain > > operations that one would expect to succeed are failing. > > > > Why are you expecting it to succeed? > > Consider: > > % svn co ^/ wc > % cd wc > % svn mkdir -mm ^/branches/foo > % svn cp trunk branches/bar > % svn ci -mm > > which should fail with 'out of date'. > > Therefore I think your case should fail as well.
In more words... when the slave hasn't synced up yet, I assume (not knowing the proxy code) that the editor would be opened against a revision N1, such that on master branches/ has been touched in some revision N2 > N1. Therefore, as far as master is concerned, the error is proper. (consistent with the FS design) Not sure if there's a good fix here... (could try to open an editor against N2 on the slave?)
