> 1. Do you want these ConflictErrors retried logs to be at level:
INFO
> 2. In addition, please specify if you feel those retried
> ConflictErrors should have their full traceback logged?
no traceback
> 3. Finally, please tell us if the ConflictErrors that *can't* be
> retried (and are return
How about adding a URL to the logged message? Something like
"See http://zope.org/ConflictError";
detailing the difference between a retried and unresovled
ConflictErrors and how to recognise them in the event.log.
___
Zope-Dev maillist - Zope-Dev@zo
1. Do you want these ConflictErrors retried logs to be at level:INFO
2. In addition, please specify if you feel those retriedConflictErrors should have their full traceback logged?
no, without traceback 3. Finally, please tell us if the ConflictErrors that *can't* be
retried (and are returned to t
Dieter Maurer wrote:
In a similar way, I could argue that "MemoryError"s are there
by design.
While it is true that *occational* "ConflictError"s are nothing
to worry about, a higher rate indicates that you soon
may come into trouble -- because the risk increases that
the automatic r
Jean-Marc Orliaguet wrote at 2005-12-4 22:28 +0100:
> ...
>In the log flle I'd like to be informed about events that are
>unexpected. Conflict errors of this kind occur "by design".
This argument is not convincing:
In a similar way, I could argue that "MemoryError"s are there
by design.
W
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Florent Guillaume wrote:
> Please vote for the level at which you want to log retried conflict
> errors. These are the ConflictErrors that aren't returned to the user
> but automatically retried by the Zope publisher.
>
> 1. Do you want these Conflict
Florent Guillaume wrote at 2005-12-2 23:00 +0100:
>Please vote for the level at which you want to log retried conflict
>errors. These are the ConflictErrors that aren't returned to the user
>but automatically retried by the Zope publisher.
>
>1. Do you want these ConflictErrors retried logs to
On Fri, 2005-12-02 at 23:00 +0100, Florent Guillaume wrote:
> 1. Do you want these ConflictErrors retried logs to be at level:
> - INFO
INFO
> - BLATHER
> - DEBUG
> - not logged
> - other
>
> 2. In addition, please specify if you feel those retried
> ConflictErrors should have their full traceba
Jean-Marc Orliaguet wrote:
In my case it's mostly filesystem-based resources (css files, or images)
accessed in read mode (zope-2.8.4). But the information no matter where
it comes from has very little value compared to other messages in the
log file, because these are completely predictable.
Dieter Maurer wrote:
Jean-Marc Orliaguet wrote at 2005-12-2 23:57 +0100:
... on what level to report retried ConflictError ...
BLATHER (I have never be able to get any meaningful information from
them, except that zope tries several times)
That's because the generated messages *were*
Florent Guillaume wrote at 2005-12-2 23:00 +0100:
>Please vote for the level at which you want to log retried conflict
>errors. These are the ConflictErrors that aren't returned to the user
>but automatically retried by the Zope publisher.
>
>1. Do you want these ConflictErrors retried logs to
Jean-Marc Orliaguet wrote at 2005-12-2 23:57 +0100:
> ... on what level to report retried ConflictError ...
>BLATHER (I have never be able to get any meaningful information from
>them, except that zope tries several times)
That's because the generated messages *were* uninformative.
You can see t
Jean-Marc Orliaguet wrote:
BLATHER (I have never be able to get any meaningful information from
them, except that zope tries several times)
That's because they excluded any useful information before. The
implementation I've put in tells you, at info level, what error actually
occurred, what o
Florent Guillaume wrote:
1. Do you want these ConflictErrors retried logs to be at level:
- INFO
2. In addition, please specify if you feel those retried ConflictErrors
should have their full traceback logged?
- No, without traceback
The actual traceback for any conflict error is pretty us
Florent Guillaume wrote:
Please vote for the level at which you want to log retried conflict
errors. These are the ConflictErrors that aren't returned to the user
but automatically retried by the Zope publisher.
1. Do you want these ConflictErrors retried logs to be at level:
- INFO
- BLATH
1. INFO
2. Yes, with traceback (necessary as these are heissenevents)
3. ERROR
4. don't care -- we can adapt
Thanks Florent for taking the lead on this. I think it's a great
help.
On Fri, 2 Dec 2005, Florent Guillaume wrote:
> Please vote for the level at which you want to log retried con
On Dec 2, 2005, at 5:00 PM, Florent Guillaume wrote:
Please vote for the level at which you want to log retried conflict
errors. These are the ConflictErrors that aren't returned to the
user but automatically retried by the Zope publisher.
1. Do you want these ConflictErrors retried logs t
1. Do you want these ConflictErrors retried logs to be at level:
INFO
2. In addition, please specify if you feel those retried
ConflictErrors should have their full traceback logged?
no traceback
3. Finally, please tell us if the ConflictErrors that *can't* be
retried (and are returned
Please vote for the level at which you want to log retried conflict
errors. These are the ConflictErrors that aren't returned to the user
but automatically retried by the Zope publisher.
1. Do you want these ConflictErrors retried logs to be at level:
- INFO
- BLATHER
- DEBUG
- not logged
- o
19 matches
Mail list logo
