Mercurial > kallithea
view docs/usage/debugging.rst @ 5979:0bb4fa32a75a
tests: Mercurial hooks must use ui.status for messages sent to the client
Mercurial changed so sys.stdout and sys.stderr now are intercepted instead of
being sent to the client. That caused a regression that
manual_test_vcs_operations.py test_push_new_file_hg caught - we no longer
reported 'Repository size' to the user.
The issue was introduced by a Mercurial change, but the fix is backwards
compatible with Mercurial 2.9.
The fix is to use ui.status everywhere. ui is a Mercurial thing, but
handle_git_receive also creates a ui object for Git hooks so ui.status can be
used there too.
| author | domruf <dominikruf@gmail.com> |
|---|---|
| date | Tue, 03 May 2016 00:12:55 +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.