Chris Withers wrote:
Philipp von Weitershausen wrote:
This would probably best be handled by one person, so if you are willing to
do all
the grepping and updating, making zLOG deprecated would just be a minor
operation :).
...but one i don't know how to perform. What code would I
Jean-Marc Orliaguet wrote:
Absolutely, this is called debugging an application (= DEBUG, TRACE).
Well, I call BS on this ;-)
Things like ConflictErrors and slow-running requests are not something
you often find out about during application development. They emerge
once the load ramps up and
Hi Dieter,
You err: I do want to see them in the logfile and
I stole Florents idea to use threadframe (in his DeadlockDebugger)
to include a traceback for long running requests in the logfile.
This way, it is
easy not only to identify long running requests but also to
get hints where they are
Summary of messages to the zope-tests list.
Period Tue Dec 6 12:01:02 2005 UTC to Wed Dec 7 12:01:02 2005 UTC.
There were 8 messages: 8 from Zope Unit Tests.
Tests passed OK
---
Subject: OK : Zope-2_6-branch Python-2.1.3 : Linux
From: Zope Unit Tests
Date: Tue Dec 6 22:15:45 EST
On Tue, Oct 25, 2005 at 03:13:11PM -0400, Jim Fulton wrote:
I just checked in a new test runner on the trunk. It is mostly backward
compatible with the old test runner. You can get help on the test runner
by running
it with -h. There is more extensive documentation in
Chris Withers wrote at 2005-12-7 10:01 +:
You err: I do want to see them in the logfile and
I stole Florents idea to use threadframe (in his DeadlockDebugger)
to include a traceback for long running requests in the logfile.
This way, it is
easy not only to identify long running requests
On Wed, Dec 07, 2005 at 10:13:36PM +0100, Dieter Maurer wrote:
| And, as we speak about replacing Zope2's ZPublisher
| by Zope3's Publisher, the old Zope2 ZPublisher will
| probably not grow such hooks any more -- but hopefully,
| the Zope3 Publisher will signal corresponding events.
It already
