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

Re: Update cache and icon overlays immediately when commit?

From: Peter McNab <mcnab_p_at_melbpc.org.au>
Date: 2006-02-08 11:25:17 CET

Nick Gilbert wrote:
> Stefan Küng wrote:
>> Nick Gilbert wrote:
>>>> If your working copy is on a network share, it is possible that
>>>> change notifications from the server are lost, so the cache doesn't
>>>> notice some changes. And if it doesn't get notified, it doesn't
>>>> recrawl the working copies - and you end up with a wrong overlay.
>>>> You can execute a "cleanup" on those working copies, which will
>>>> invalidate the cached status for all dirs below the one you
>>>> selected for cleanup. By doing that, the cache will recrawl that
>>>> working copy and the overlays will match again.
>>> Stefan, my working copy is on a local HDD and I have noticed this
>>> bug too. In fact I reported it quite a while ago on this list and
>>> never got a reply. Even pressing F5 does not help the icons update.
>>> The only way to get the icons to be correct is to go INTO the folder
>>> that is marked as having changes, then back out again. Once you have
>>> done that, the green tick appears as it should.
>> Since that hasn't happened on my machine for some time now, I need
>> some kind of reproduction recipe here. Otherwise I can't find out
>> why/how this happens and can't fix it.
> It doesn't always happen, but basically I just modify a file inside a
> subfolder of my working copy, then commit. The status icon never
> changes to a green tick unless I go into that folder and back up
> again. Nothing more complex than that. About 60% of the time it works
> OK, and rest of the time it doesn't. I haven't worked out any pattern
> as to why it works sometimes and why it doesn't work other times.
> Nick...
Over that past couple of weeks, not that I've done a whole lot of
committing, the responsiveness does seem to have reduced from being good
to "ordinary". In particular one really misleading piece of behavior
occurred while a tree of changes was being committed.
In that instance I had one Explorer window showing the root node of the
commit tree (from which the commit was launched) and another Explorer
Window open further into the tree.
After the commit two of the affected folder's icons failed to update.
F5..ed to no avail.
Navigated into and out of each folder in turn and one still failed to
F5..ed again to no avail.
Then closed the deeper Explorer window.
Navigated into and out of the affected folder and the icon finally updated.
Cannot nominate the O/S (XP or W2K) or the particular nightly or release
revision, sorry.
Didn't report it then, there seemed to be enough going on at the time.


To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Wed Feb 8 11:25:39 2006

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.