On 2012-05-10 00:46, Bart van der Schans wrote:
Hi,
A small update about the 2.4.2 release. Unfortunately I found yet
another bug which causes data inconsistencies. This time it's related
to the handling of node.refresh(). I do have a concurrent stress test
which can consistently reproduce this, but not a clear reproduction
path yet. Since we are in the process of chasing down this bug I want
to hold of the 2.4.2 release for a little bit longer so we hopefully
have a fix for this issue in the release. I will open a jira issue so
other people can have a look as well.
...
Bart, any news on this? I'd prefer a 2.4.2 release as soon as possible,
no matter whether this fix makes it or not :-)
Best regards, Julian
