Yeah, it's running 2.2.1b1 and it's still hosed. :-( When Ethan gets
back from LinuxWorld, I'm going to try to have him update to the latest
CVS and see if we can pin the problem down.
I added logging code to the catalog that was *supposed* to make it
easier to track down why these keyerrors were happening. However, I
muffed it and the current Zope 2.2.1b1 release logs errors on all
fieldindex uncatalog_object calls (no matter if there's a problem or
not). That particular problem is fixed in CVS.
We need to get a chance to examine the error output from index-unindex
functions to see exactly what's going on with the catalog. I
desperately need to fix this problem for reasons unrelated to zope.org.
If anyone is running a current CVS checkout of the Zope 2.2 branch, and
they're having KeyErrors, if you can send me relevant sections of your
stupid_log_file, I'd be grateful. Maybe I can establish a pattern. But
please don't send me log files with hundreds of unindex_object calls ala
Zope 2.2.1b1, it needs to be the latest CVS checkout on the 2.2 branch.
"Bak @ kedai" wrote:
> is Zope.org running 2.2.1b1 or CVS? cause i think key error still occurs.
> check out 'What's New' at Zope.org, and you'll get the error.
> i might be wrong though
> Zope maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://lists.zope.org/mailman/listinfo/zope-dev )
Publishers of Zope - http://www.zope.org
Zope maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -