|
We think we've figured out the cause of this problem. It's a combination of a few things, including a hole in our logic for handling a particular condition that can arise. Solving it involves multiple pieces, but we've outlined a plan that should work well. So we should have this fixed in the next release, although that's not likely to be until early next week.
Thanks for your patience! And for sending in your databases so that we could figure this thing out!
|