How to report problems with the cache

Hi,

While I really appreciate all your reports about the cache and overlays
not working right, those reports usually miss important information.
Sometimes because you just forget, and sometimes because you guys assume
something on the cache internals which isn't right. So I'd like to give
you a small guide what to include in your reports:

- ALWAYS: version and revision number of the build you're using
- is the overlay wrong only until you hit F5?
   --> indicates a problem with the shell refresh, and that's
       something I blame MS for ;)
- If you hit F5 (please only once, then wait a minute), does
   the overlay change to the correct one?
   --> indicates that the cache is working correctly, but
       the crawler hasn't finished yet (big working copy?)
- If you navigate into the folder with the wrong overlay,
   does it change back?
   --> indicates a problem with the cache. Either the change in
       a file wasn't noticed, or that change hasn't been propagated
       up in the tree.
- Does the cache use a lot of CPU time?
   --> indicates the cache is either busy or working on an endless
       loop, which would mean a really bad bug.
- Do you see disk activity you don't know exactly where its from?
   --> could indicate that the cache is crawling working copies,
       but if that doesn't stop it could indicate that the crawler
       crawls the same folder(s) over and over again.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org