Bug 7533 - writes to stderr although there are no errors
Summary: writes to stderr although there are no errors
Status: RESOLVED INVALID
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: sa-compile (show other bugs)
Version: 3.4.1
Hardware: PC Linux
: P2 normal
Target Milestone: Undefined
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-14 15:53 UTC by ente
Modified: 2018-01-14 22:00 UTC (History)
2 users (show)



Attachment Type Modified Status Actions Submitter/CLA Status

Note You need to log in before you can comment on or make changes to this bug.
Description ente 2018-01-14 15:53:09 UTC
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
Comment 1 Bill Cole 2018-01-14 18:18:07 UTC
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)
Comment 2 ente 2018-01-14 22:00:01 UTC
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...