Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

consider if the default logger could put logs to stderr instead of stdout #768

Closed
Tracked by #770
sio4 opened this issue Sep 17, 2022 · 0 comments · Fixed by #782
Closed
Tracked by #770

consider if the default logger could put logs to stderr instead of stdout #768

sio4 opened this issue Sep 17, 2022 · 0 comments · Fixed by #782
Assignees
@sio4
Labels
s: fixed was fixed or solution offered
Milestone
v6.0.7

Comments

@sio4
Copy link
Member

sio4 commented Sep 17, 2022

consider if the default logger could put logs to stderr instead of stdout.

<...> One more point. I think the current behavior, printing the logs to the stdout is not a good choice so I will fix it soon.

Originally posted by @sio4 in #622 (review)
@sio4 sio4 added the s: triage Some tests need to be run to confirm the issue label Sep 17, 2022
@sio4 sio4 self-assigned this Sep 17, 2022
@sio4 sio4 modified the milestones: v6.0.7, Backlog Sep 17, 2022
This was referenced Sep 20, 2022
Closed
Merged
@sio4 sio4 closed this as completed in #782 Sep 24, 2022
@sio4 sio4 added s: fixed was fixed or solution offered and removed s: triage Some tests need to be run to confirm the issue labels Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sio4 sio4

Labels
s: fixed was fixed or solution offered
Projects
None yet
Milestone
v6.0.7
Development

Successfully merging a pull request may close this issue.

made default logger to print output to stderr instead of stdout gobuffalo/pop
1 participant
@sio4