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

Re: Log Cache problem on a branch doesn't show latest revision

From: Stefan Fuhrmann <stefanfuhrmann_at_alice-dsl.de>
Date: Thu, 10 Sep 2009 15:53:17 +0200

Lübbe Onken <luebbe.tortoisesvn_at_googlemail.com> wrote:

> > If that is not possible,
> > create a local copy of that file so we have it available for
> > further tests.
> Forgive the stupid question. Where do I find the cache file?


> >> I assume that the problem will probably go away when I delete the log
> >> cache for this repository, but I wanted to report this first.
> >
> > Will<CTRL>-<F5> fix the problem?
> Haven't thought of this :)
> If I press Ctrl-F5, the head revision of the branch is shown (in bold).
> If I press just F5, the head revision goes away again.

That is weird; it means that the right data is requested
from the repository but somehow doesn't make it to the
log cache.

To narrow the problem down, please do the following

* Create a backup of the log cache file (or whole folder).

* Export cache content: "Settings -> Cached Repos ->
  select the broken one -> Export".

* Show "Details" for the same cache. Is "Skip Ranges" > 0?
  Is "Max Revision" equal or greater than the missing one?

* Does "Update" (same place) fix the problem?
  If so, restore from backup.

* Is "Settings -> Log Cache -> HEAD Timeout" set?
  If so, set it to 0 and retry.

* Log for the project root (e.g. via repo browser).
  Does the revision show up?

* Does the revision graph show all revisions (make sure
  to show all revisions)?

* Go to the CSV files exported earlier. Open *.revisions.csv
  in an arbitrary text editor (it is sorted by revision).
  Does it contain an entry for the missing revision?

Remote diagnosis is hard ;)

-- Stefan^2.


To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-09-10 15:53:18 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

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