Mercurial > kallithea
view docs/usage/debugging.rst @ 7603:0e8e55f954be
style: avoid double horizontal padding inside panel-body
Only give inline-comments padding if they actually appear inside a diff. General comments already have padding from .panel-body.
Drop padding on changesets columns (next to graphs). The graph already has space, and .panel-body gives spacing to the right.
Drop extra column padding for repo and PR summaries that use columns. The columns already have some padding from .panel-body.
author | Mads Kiilerich <mads@kiilerich.com> |
---|---|
date | Fri, 22 Mar 2019 02:14:36 +0100 |
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.