You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2018/01/14 15:53:09 UTC
[Bug 7533] New: writes to stderr although there are no errors
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7533
Bug ID: 7533
Summary: writes to stderr although there are no errors
Product: Spamassassin
Version: 4.0.0
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: sa-compile
Assignee: dev@spamassassin.apache.org
Reporter: ente@ck76.de
Target Milestone: Undefined
sa-compile writes to stderr instead of stdout for the following lines:
Jan 14 16:44:52.495 [15017] info: generic: base extraction starting. this can
take a while...
Jan 14 16:44:52.496 [15017] info: generic: extracting from rules of type body_0
100% Completed 5913.17 rules/sec in 00m00s
....................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................
100% Completed 877.55 bases/sec in 00m02s
Jan 14 16:44:55.314 [15017] info: body_0: 1154 base strings extracted in 3
seconds
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7533] writes to stderr although there are no errors
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7533
--- Comment #2 from ente <en...@ck76.de> ---
The fact that you can harness a horse to your car doesn't fix your broken
engine, does it?
Yes. This is not a major bug. It's rather a hassle. I don't mind if you answer:
hell, yea: but right now I don't have time and later I prefer to play with my
kids. Well! Enjoy your kids. I mean it. I don't mind the error as much as I
would mind a kid being unhappy.
I tried to get a summary of all failed steps in a long script. They should be
logged to a separate script. The problem is: if you read 200 lines of errors
each day, what will happen after 200 day it suddenly becomes 206 lines?
Now: STDERR sounds like error. My simple question is: is your software
errorneous is the sound of STDERR? Maybe STDdiagnostic would sound better?
Please rephrase stderr to stdiag or mark this thing as a "hell of unimportant
bug". But please don't tell me this is not a bug. This would render mine and
your time useless. I hate to waste my time. Unless I play with other kids...
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7533] writes to stderr although there are no errors
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7533
Bill Cole <sa...@billmail.scconsult.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa-bugz-20080315@billmail.s
| |cconsult.com
Resolution|--- |INVALID
Status|NEW |RESOLVED
--- Comment #1 from Bill Cole <sa...@billmail.scconsult.com> ---
Working as designed.
The stderr stream is for diagnostic messages, not solely errors. These are
informational messages from sa-compile noting its progress, while the stdout
stream is primarily coming from tools sa-compile uses.
If you want to merge the stdio streams you can do so externally (i.e. 2>&1)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7533] writes to stderr although there are no errors
Posted by bu...@bugzilla.spamassassin.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7533
ente <en...@ck76.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ente@ck76.de
Version|4.0.0 |3.4.1
--
You are receiving this mail because:
You are the assignee for the bug.