On 2009-09-20 at 13:18:55 [+0200], Niels Reedijk <niels.reedijk@xxxxxxxxx> wrote: > 2009/9/20 Oliver Tappe <zooey@xxxxxxxxxxxxxxx>: > > > > On 2009-09-20 at 08:42:02 [+0200], Niels Reedijk <niels.reedijk@xxxxxxxxx> > > wrote: > >> > >> 2009/9/20 root on svn <root@xxxxxxxxxxxxxxxx>: > >> [ ... ] > > Last thing yesterday, I did a trac-admin resync, such that the test > > installation of trac should reflect the current state of the corresponding > > svnsync repo. > > Yes, that's what I thought, because the 'strange' changeset (4###) > with user svnsync and dated today (instead of 6 years ago) > disappeared. > > This could be a warning of a (potential) issue in the future though. > What happens is that svnsync commits a revision (as user svnsync and > dated today), then releases the lock and afterwards changes the > metadata. > > Trac checks every page load whether the repository has changed. If a > new changeset is added, it will load (and cache) its data. Now if > someone requests a page before svnsync has updated the metadata, then > that means that the cached data is inconsistent (and that would mean a > manual trac-admin resync when that happens). > > Now this might be such a rare occasion (once a year) that we decide it > is not the effort to look into it, so we might just wait until it > happens some day and then see what to do, but if there is something > that we can do to fix it now I am open for suggestions. I think what we can do is to wait until the issue comes up again and in that case try to invoke trac-admin <path> resync <revision> which (according to the docs) should resync just that revision. cheers, Oliver