Re: [Zope-dev] Re: Logging after ConflictError Retries

2005-06-10 Thread Dieter Maurer
Dieter Maurer wrote at 2005-6-10 20:43 +0200: >Malcolm Cleaton wrote at 2005-6-10 11:00 +0100: >> ... 2. If there is at least one ConflictError and then the request finishes with an error (either more ConflictErrors or something else), the Z2 log shows the request as having been answere

Re: [Zope-dev] Re: Logging after ConflictError Retries

2005-06-10 Thread Dieter Maurer
Malcolm Cleaton wrote at 2005-6-10 11:00 +0100: > ... >>>2. If there is at least one ConflictError and then the request finishes >>>with an error (either more ConflictErrors or something else), the Z2 log >>>shows the request as having been answered with status 200, although >>>actually a status 50

[Zope-dev] Re: Logging after ConflictError Retries

2005-06-10 Thread Malcolm Cleaton
On Thu, 09 Jun 2005 20:50:22 +0200, Dieter Maurer wrote: > The fix is (almost surely) to replace in ".../Zope/App/startup.py": > >if t is ZPublisher.Retry: v.reraise() > > by > >if t is ZPublisher.Retry: t, v, traceback = v._args Yes, that's better than my fix. >>2. If there is at lea

[Zope-dev] Re: Logging after ConflictError Retries

2005-06-09 Thread Malcolm Cleaton
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