##// END OF EJS Templates
tests: fix failures due to environment LANG settings (Issue #286)...
tests: fix failures due to environment LANG settings (Issue #286) When the environment in which the tests are run dictates a non-English language (e.g. via LANG=de_DE.UTF-8), certain tests started to fail because formencode validation messages where translated in that language. A test failing this way is for example test_create_in_group_without_needed_permissions in kallithea/tests/functional/test_admin_repos.py . This is a regression of commit 3b29103657df (i18n: remove explicit formencode language setting), but in fact reverting it is not the right solution as there is no problem except during test execution. Instead, force the formencode language to 'empty' (meaning English) for test execution only. See also http://www.formencode.org/en/latest/i18n.html

File last commit:

r5817:87ac42db default
r6694:c20abcf4 default
Show More
debugging.rst
33 lines | 1.2 KiB | text/x-rst | RstLexer

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.