Mercurial > kallithea
view docs/usage/debugging.rst @ 7986:25f6f0c54e0f stable
bin/ldap_sync: revert commit 04dee6fdfdff
Commit 04dee6fdfdff fixed an apparent problem detected by isort, but as Mads
Kiilerich pointed out, it was caused by an incomplete virtualenv that did
not include 'python-ldap'. As a result, isort would not consider 'ldap' as a
standard module and treated it as a local module.
A subsequent commit will fix the 'make-release' script to install all
expected dependencies.
| author | Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> |
|---|---|
| date | Sat, 30 Nov 2019 20:44:45 +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.