John Barratt wrote at 2005-6-9 16:54 +1000:
> ...
>I would hence suspect the wrapping, and/or behaviour of the object
>and/or context to be somehow different?
A long time ago, Shane posted a very useful function
to analyse acquisition wrappers: "showaq".
Maybe, the mailing list archive is still
Malcolm Cleaton wrote at 2005-6-9 10:13 +0100:
>After a ConflictError causes a request to be retried, a few things go a
>bit wrong with error handling and logging in the Zope server.
>
>1. If the request is abandoned after repeated ConflictErrors, no error at
>all appears in the error log.
Right:
Heads up for the 2.8.0 final release. My plans are to make the final
release on Saturday morning. So any further changes should be done by
tomorrow at the latest.
Cheers,
-aj
pgptJAh1rk5y3.pgp
Description: PGP signature
___
Zope-Dev maillist - Zop
> -Original Message-
> From: Chris McDonough [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, 8 June 2005 11:56 AM
> To: Dylan Jay
> Cc: zodb-dev@zope.org
> Subject: Re: [ZODB-Dev] Generational Caching
>
> One way to potentially soften the impact of cache busting by spiders
> might be t
On Thu, 09 Jun 2005 10:13:05 +0100, Malcolm Cleaton wrote:
> 162,163c162
> < if REQUEST.supports_retry():
> < raise ZPublisher.Retry(t, v, traceback)
> ---
> > raise ZPublisher.Retry(t, v, traceback)
I just noticed I've generated this patch backw
After a ConflictError causes a request to be retried, a few things go a
bit wrong with error handling and logging in the Zope server.
1. If the request is abandoned after repeated ConflictErrors, no error at
all appears in the error log.
The following change to Zope/App/startup.py appears to fix
