-
Notifications
You must be signed in to change notification settings - Fork 140
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.
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
Logger repeats logs #432
Comments
The first one is a log from gunicorn, and the second is from flask. I wrestled with this again for a while with a recent PR (https://github.com/NYUCCL/psiTurk/pull/483/files), but I think I decided it was necessary to have both, I can't remember. But flask routes need to be able to log, and so does gunicorn. |
Can they be separated into two log files then? |
Not for situations that need stream logging, like cloud providers. I wish I
had kept notes on what I saw during that PR, I remember having a lot more
insight into what was going on and why...
…On Mon, May 3, 2021, 9:51 PM jacob-lee ***@***.***> wrote:
Can they be separated into two log files then?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#432 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAI6Y7K7A4UXNNYVCMD6UWLTL5VNVANCNFSM4PHSPX2A>
.
|
Here are a couple ideas.
- preface log entries with source (e.g. gunicorn, flask, etc.); am pretty
sure I've done something similar before.
- allow different logging levels for gunicorn and flask. Seems like we'd
only want warning and above most of the time for gunicorn
On Tue, May 4, 2021 at 12:44 AM Dave Eargle ***@***.***>
wrote:
… Not for situations that need stream logging, like cloud providers. I wish I
had kept notes on what I saw during that PR, I remember having a lot more
insight into what was going on and why...
On Mon, May 3, 2021, 9:51 PM jacob-lee ***@***.***> wrote:
> Can they be separated into two log files then?
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <#432 (comment)>,
or
> unsubscribe
> <
https://github.com/notifications/unsubscribe-auth/AAI6Y7K7A4UXNNYVCMD6UWLTL5VNVANCNFSM4PHSPX2A
>
> .
>
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#432 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAM5SQOPXXJPIRTJ2JIPLQ3TL53RTANCNFSM4PHSPX2A>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Logging is repeating messages. Perhaps handlers are being added more than once?
Python: 3.8
Psiturk: github master today
Reproduction:
Correct output:
[2020-07-25 14:10:33 -0400] [15478] [ERROR] Reached /my_custom_view
Actual output:
The text was updated successfully, but these errors were encountered: