Chris Hofmann wrote:
> There was a big spike in "2.0 branch" nt.ddl crashes on May 31. That
> might have corresponded to more usage of alpha 3 when folks returned
> from the Memorial day holiday in the US.
This is probably due to turning back on Mork autocomplete. See bug 339861.
This is a huge problem, and I've been so far unable to reproduce it. It
seems that basically nobody has done any testing. Hopefully this post
will cause somebody that does see this problem to help out.
Since this just re-enabled old working code, I suspect that one of the
changes checked in on or after Storage autocomplete was first enabled is
causing the problem. We would not have noticed the problems because it
There are two options:
Option 1: Revert back to Storage form autocomplete. This should
immediately fix the problem, but will ensure that Mork autocomplete will
stay permanently broken because nobody is testing it. The storage
autocomplete is also not as well tested, and needs some work before
release for some things like recovering in case of a corrupted database
(currently it will just be permanently broken).
Option 2: Find the problem and fix the Mork version. This has the
disadvantage of taking longer and pissing people off.
I'm OK with either of these options. However, if we do (1), I feel that
we should delete Mork autocomplete from toolkit, which I imagine people
will be opposed to.