Mercurial > kallithea
view docs/usage/debugging.rst @ 7907:b42ee1bdf082
wsgi: make WSGI wrapper follow the result and log when it actually has finished
The wrapper lost control after "%s responding after %.3fs" when it passed the
iterator through.
Now, wrap the iterator and keep track of its use and when it is closed and make
an additional loging of "%s responded after %.3fs".
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Sat, 19 Oct 2019 23:07:12 +0200 |
parents | 87ac42db389c |
children |
line wrap: on
line source
.. _debugging: =================== Debugging Kallithea =================== If you encounter problems with Kallithea, here are some instructions on how to debug them. .. note:: First make sure you're using the latest version available. Enable detailed debug --------------------- Kallithea uses the standard Python ``logging`` module to log its output. By default only loggers with ``INFO`` level are displayed. To enable full output change ``level = DEBUG`` for all logging handlers in the currently used .ini file. This change will allow you to see much more detailed output in the log file or console. This generally helps a lot to track issues. Enable interactive debug mode ----------------------------- To enable interactive debug mode simply comment out ``set debug = false`` in the .ini file. This will trigger an interactive debugger each time there is an error in the browser, or send a http link if an error occurred in the backend. This is a great tool for fast debugging as you get a handy Python console right in the web view. .. warning:: NEVER ENABLE THIS ON PRODUCTION! The interactive console can be a serious security threat to your system.