Same log line output twice?
See original GitHub issueI add this line below in my code.
logger.add(sys.stdout, colorize=True, format="<green><b>{time:YYYY-MM-DD :mm:ss}</b></green> - {level} - {file} - {line} - {message}")
The same log output twice in terminal like:
2022-03-31 18:19:10.853 | INFO | main:main:33 - Set random seed to 1 2022-03-31 :19:10 - INFO - train.py - 33 - Set random seed to 1
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
log messages appearing twice with Python Logging
And for some reason, all the messages are appearing twice. I commented out one of the stream handlers, still the same thing. Bit...
Read more >Duplicate Logging Messages in Python - jdhao's digital space
When I am working on a project, I find that the same message is printed twice. The following minimal code can reproduce this...
Read more >4.4.3 - log[] is reading the same lines twice - ZABBIX Forums
For some reason my zabbix agent appears to be reading the same lines twice. It grabs only the newest values (so it's not...
Read more >A Step-by-Step Guide to Python Logging - Pylenin
A comprehensive guide to understanding the advantages and usage of Python Logging module.
Read more >Why Log statement is printing twice in console log file.
In some cases, logging output is executed twice to a log destination. This is a side effect of the Log4j additivity which is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sorry, I forgot to answer you. To be honest, I prefer not to overload the current README. I quite like its relative simplicity with examples and links to the documentation for details.
I’m closing this ticket as I answered the initial question, but a new one can be opened about possible documentation improvements.
@Delgan From the sounds of it, a discussion surrounding documentation architecture might be good. A good start might just include adding a table of contents to the README. What do you think?