Tim Peters wrote:
Same answer as before: someone who understands the intended
invariants during cache verification needs to stare at the mutually
inconsistent code and comments, and figure out was intended.
Is there a list of suspects for this?
>> (or at least change it and see what happens?
[Dieter M]
Almost surely, the code should be "cur_tid <= tid" rather than
"cur_tid < tid". But there is nobody that is sure about it.
[Chris W]
Well, as I've asked before, what needs to happen for someone to _become_
sure about it?
Same answer as before: someone who understands the intended
[EMAIL PROTECTED] wrote:
Almost surely, the code should be "cur_tid <= tid" rather than
"cur_tid < tid". But there is nobody that is sure about it.
Well, as I've asked before, what needs to happen for someone to _become_
sure about it?
(or at least change it and see what happens? ;-) )
chee
Sven Schomaker wrote at 2006-7-4 14:21 +0200:
> ...
>I just upgraded to Zope 3.2.1 and changed my setup to use a
>ZEO backend. This results in the exception below. Returning
>to the standard FileStorage backend everything works fine.
> ...
> File "/usr/local/Zope-3.2.1/lib/python/ZEO/ClientStorag
