Zandronum Chat on our Discord Server Get the latest version: 3.1
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003372Doomseeker[All Projects] Bugpublic2018-02-15 02:052018-10-27 22:55
ReporterZalewa 
Assigned ToZalewa 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.1 
Target Version1.2Fixed in Version1.2 
Summary0003372: Diagnostics messages are written to stdout (instead of stderr)
DescriptionDoomseeker's startup logs (etc) are like diagnostics messages, but treated as normal output from the program. This goes against POSIX' description of stderr:

Quote
At program start-up, three streams shall be predefined: [...] standard output (for writing conventional output), and standard error (for writing diagnostic output).


stdout makes sense for --version-json as conventional JSON output, but the diagnostics messages should really be changed from stdout to stderr.
Steps To ReproduceOn Unix-like machines:

doomseeker 1>/tmp/stdout.log 2>/tmp/stderr.log


See /tmp/stdout.log and /tmp/stderr.log for messages of the appropriate standard stream.
Additional Information

  • http://pubs.opengroup.org/onlinepubs/9699919799/functions/stderr.html

  • https://www.gnu.org/software/libc/manual/html_node/Standard-Streams.html

  • https://unix.stackexchange.com/q/331611/

Attached Files

- Relationships
related to 0003282closedZalewa Omitting file from --version-json command line parameter doesn't print to standard output 

-  Notes
User avatar (0019042)
WubTheCaptain (reporter)
2018-02-15 02:08

This was fixed:'https://bitbucket.org/Doomseeker/doomseeker/commits/87122ce09493fbad5fe718acf64ef2950167fd13 [^]'

I thought of submitting a bug for the bug tracker for future reference, anyway.
User avatar (0019043)
WubTheCaptain (reporter)
2018-02-15 02:21
edited on: 2018-02-15 03:20

Interestingly enough, I would like to reopen this issue for more discussion.

One of the answers in the linked Unix & Linux Stack Exchange thread argues whether POSIX-like programs should be quiet by default (that's an Unix-y thing to do), and only output to stderr if the exit status was non-zero. To quote:

Quote from POSIX.1-2008, 1.4 Utility Description Defaults
Default Behavior: When this section is listed as "The standard error shall be used only for diagnostic messages.", it means that, unless otherwise stated, the diagnostic messages shall be sent to the standard error only when the exit status indicates that an error occurred and the utility is used as described by this volume of POSIX.1-2008.


Do we need to introduce a command line flag for --quiet or --verbose? I'd keep them to stderr, though.

User avatar (0019044)
WubTheCaptain (reporter)
2018-02-15 02:30

Quote from WubTheCaptain
I'd keep them to stderr, though.


Haha disregard that, stdout probably makes more sense with a --verbose (or -v) flag with quiet by default behavior. Anyone agree?

stderr for real diagnostics errors, though.
User avatar (0019050)
Zalewa (developer)
2018-02-15 07:37

--version-json could indeed benefit from not being spammed with stderr logs by default
User avatar (0019051)
Zalewa (developer)
2018-02-15 08:41

"--quiet" and "--verbose" added here:'https://bitbucket.org/Doomseeker/doomseeker/commits/53e2af801b780f3d233bd8a24ea558535d887efd [^]'
User avatar (0019748)
WubTheCaptain (reporter)
2018-09-25 03:11
edited on: 2018-09-25 03:12

As said, this has been resolved.

Side-note: It seems like --verbose is useless at this point and --quiet works as intended. The output isn't quiet by default (except on stdout), but uh, we don't do much with stdout anyway. It's not like Doomseeker had stdout of its server lists in some specific format for other applications to use.


Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-02-15 02:05 WubTheCaptain New Issue
2018-02-15 02:05 WubTheCaptain Status new => assigned
2018-02-15 02:05 WubTheCaptain Assigned To => Zalewa
2018-02-15 02:06 WubTheCaptain Relationship added related to 0003282
2018-02-15 02:06 WubTheCaptain Reporter WubTheCaptain => Zalewa
2018-02-15 02:06 WubTheCaptain Status assigned => resolved
2018-02-15 02:06 WubTheCaptain Resolution open => fixed
2018-02-15 02:06 WubTheCaptain Fixed in Version => 1.2
2018-02-15 02:08 WubTheCaptain Note Added: 0019042
2018-02-15 02:21 WubTheCaptain Note Added: 0019043
2018-02-15 02:21 WubTheCaptain Status resolved => feedback
2018-02-15 02:21 WubTheCaptain Resolution fixed => reopened
2018-02-15 02:23 WubTheCaptain Summary Logs are written to stdout instead of stderr => Diagnostics logs are written to stdout (instead of stderr)
2018-02-15 02:27 WubTheCaptain Summary Diagnostics logs are written to stdout (instead of stderr) => Diagnostics messages are written to stdout (instead of stderr)
2018-02-15 02:30 WubTheCaptain Note Added: 0019044
2018-02-15 03:20 WubTheCaptain Note Edited: 0019043 View Revisions
2018-02-15 07:37 Zalewa Note Added: 0019050
2018-02-15 07:37 Zalewa Status feedback => assigned
2018-02-15 08:41 Zalewa Note Added: 0019051
2018-02-15 08:41 Zalewa Status assigned => needs testing
2018-09-25 03:11 WubTheCaptain Note Added: 0019748
2018-09-25 03:11 WubTheCaptain Status needs testing => resolved
2018-09-25 03:11 WubTheCaptain Resolution reopened => fixed
2018-09-25 03:12 WubTheCaptain Note Edited: 0019748 View Revisions
2018-10-27 22:55 WubTheCaptain Status resolved => closed






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2024 MantisBT Team
Powered by Mantis Bugtracker