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

[Lennart Regebro]

On Thu, Apr 8, 2010 at 10:56, ChrisW <chris at simplistix.co.uk> wrote:
> 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...

Can we have a state for "weird errors that can't be reproduced but
needs to be kept here for future reference"? I can see the use of
that, so we can keep track of whom it happens too and how often.

-- 
Lennart Regebro: Python, Zope, Plone, Grok
http://regebro.wordpress.com/
+33 661 58 14 64

-- 
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.