RE: [ZODB-Dev] Different weird errors with Zope 2.8.4
[Chris Withers] > Yay! Where's the correct place to report these nowadays? Same as always: ZODB bugs should be reported on a Zope Collector, with topic Database. It's fine to discuss them on zodb-dev, but when (as appears to be the case with this one) nobody has an immediate answer or time to dig into it, opening a collector issue is the way to proceed. If it's only in the mailing list archives, it will be forgotten by all within a week (although it may cheer someone with the same problem 3 years from now when they happen to stumble into the old message while doing a web search ;-)). ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] Different weird errors with Zope 2.8.4
Yay! Where's the correct place to report these nowadays? cheers, Chris Dieter Maurer wrote: Chris Withers wrote at 2005-11-29 14:33 +: Hot on the heals of my posts about "Shouldn't load state for" comes the eagerly awaited sequel "Couldn't load state for" ;-) ... File "lib/python/ZEO/zrpc/connection.py", line 531, in call r_flags, r_args = self.wait(msgid) File "lib/python/ZEO/zrpc/connection.py", line 648, in wait self.replies_cond.release() File "lib/python2.3/threading.py", line 113, in release assert self.__owner is me, "release() of un-acquire()d lock" AssertionError: release() of un-acquire()d lock Looks like a ZEO bug (more precisely a "ZEO.zrpc.conntection" bug). Probably a race condition. -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
Re: [ZODB-Dev] Different weird errors with Zope 2.8.4
Chris Withers wrote at 2005-11-29 14:33 +: >Hot on the heals of my posts about "Shouldn't load state for" comes the >eagerly awaited sequel "Couldn't load state for" ;-) > ... > File "lib/python/ZEO/zrpc/connection.py", line >531, in call > r_flags, r_args = self.wait(msgid) > File "lib/python/ZEO/zrpc/connection.py", line >648, in wait > self.replies_cond.release() > File "lib/python2.3/threading.py", line 113, >in release > assert self.__owner is me, "release() of un-acquire()d lock" >AssertionError: release() of un-acquire()d lock Looks like a ZEO bug (more precisely a "ZEO.zrpc.conntection" bug). Probably a race condition. -- Dieter ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev
[ZODB-Dev] Different weird errors with Zope 2.8.4
Hot on the heals of my posts about "Shouldn't load state for" comes the eagerly awaited sequel "Couldn't load state for" ;-) Here's the errors: 2005-11-29T14:24:24 ERROR ZODB.Connection Couldn't load state for 0x6a7ed9 Traceback (most recent call last): File "lib/python/ZODB/serialize.py", line 488, in getState return unpickler.load() File "lib/python/DateTime/DateTime.py", line 513, in __init__ raise SyntaxError('Unable to parse %s, %s' % (args, kw)) SyntaxError: (, , (None,)) 2005-11-29T14:24:25 ERROR ZODB.Connection Couldn't load state for 0xdba819 File "lib/python/ZEO/zrpc/connection.py", line 531, in call r_flags, r_args = self.wait(msgid) File "lib/python/ZEO/zrpc/connection.py", line 648, in wait self.replies_cond.release() File "lib/python2.3/threading.py", line 113, in release assert self.__owner is me, "release() of un-acquire()d lock" AssertionError: release() of un-acquire()d lock Anyone seen either of these and/or have a hit as to what's causing them? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk ___ For more information about ZODB, see the ZODB Wiki: http://www.zope.org/Wikis/ZODB/ ZODB-Dev mailing list - ZODB-Dev@zope.org http://mail.zope.org/mailman/listinfo/zodb-dev