statdaemon extension

[Martin Geisler]

Martin Geisler <mg at aragost.com> writes:

> Idan Kamara <idankk86 at gmail.com> writes:
>
>> On Tue, Aug 21, 2012 at 1:59 PM, Martin Geisler <mg at aragost.com> wrote:
>>>
>>>   https://bitbucket.org/aragost/statdaemon
>>>
>>> With the big tree, I see stale results in 'hg status', even though I
>>> see that the statdaemon is updating its cache when I make changes. I
>>> haven't tracked this down yet and the tests (yay, tests on Windows!)
>>> haven't captured it yet.
>>
>> Pretty sure the file notification API is known to sometimes fail to
>> report some changes. Especially when there's a burst of incoming
>> changes that cause some underlying buffer to fill up.
>
> Right, that something I need to detect and handle too!

That should now be handled! The daemon will clear its cache if it sees a
overflow of the buffer. That way the cache will be rebuilt from scratch
on the next 'hg status' call.

> Here it mustbe something simpler -- I'm just modifying a file five
> directories down in the working copy. I can see that the statdaemon
> gets the event from the OS and refreshes its cache -- but the client
> doesn't see it.

It turned out that I didn't pconvert the paths that came via file system
events from Windows and so the cache ended up with a mix of 'x/y/z' and
'x\y\z' paths.

I would be grateful to hear back from people who try the extension...
I've only tested it on Windows 7, but the hope is that it works all the
way back to Windows XP.

-- 
Martin Geisler

aragost Trifork
Commercial Mercurial support
http://aragost.com/mercurial/