[zope2-tracker] [Bug 143593] Re: ConflictErrors cause "Shouldn't load state for?"

[ChrisW]

Lennart Regebro wrote:
> On Thu, Apr 8, 2010 at 10:20, ChrisW <chris at simplistix.co.uk> wrote:
>> "This bug report will be marked for expiration in 58 days if no further
>> activity occurs."
> 
> Sounds fair to me. More info on how to reproduce the bug should be
> forthcoming withing 58 days then, we hope? :-)

Actually, no. This was a hard-to-reproduce error that only occurred 
under high load.

Closing it off will just mean that we start the process again, rather 
than having this issue open and available as a container for the error 
reports...

Chris

-- 
Simplistix - Content Management, Batch Processing & Python Consulting
             - http://www.simplistix.co.uk

-- 
ConflictErrors cause "Shouldn't load state for?"
https://bugs.launchpad.net/bugs/143593
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.