Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[BUG] Logging configuration when running bokeh server
See original GitHub issueIn Bokeh 1.1.0, when a bokeh application is run on a bokeh server, configuration of the root logger inside the user application via logging.basicConfig or bokeh.utils.logconfig.basicConfig is ignored. This is because basicConfig has already been called when the bokeh server is started and has already assigned a handler to the root logger. The logging.basicConfig function does nothing when a handler is already assigned, which is expected behavior. Documentation on the bokeh server page could help a user to know that to modify the root logger behavior within a program, the root logger handlers must be accessed directly.
Issue Analytics
- State:
- Created 4 years ago
- Comments:13 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’ll take a swing at it after the weekend. I agree, python logging is deeply confusing!
@lunarspectrum The bug is simpler only on the surface. A proper solution should not require fiddling with already configured handlers.