Tres Seaver wrote:
Module ZODB.Connection, line 814, in _setstate_noncurrent

This is on Zope 2.9.4.

Any ideas?

Have you looked at the code?

Yup, sure did.

I can only guess that _setstate_noncurrent is called when the mvcc code decides it needs data from state that isn't the latest for an object.

Unfortunately, neither of the asserts, including the failing one, have any comments anywhere near them. It's not at all clear what they're trying to protect again and I certainly have no idea why they might be tripping :-/


Simplistix - Content Management, Zope & Python Consulting

Zope-Dev maillist  -
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to