kallithea Files · docs/usage/debugging.rst

Files @ 5d524b9246d8

Branch filter:

Location: kallithea/docs/usage/debugging.rst

5d524b9246d8 1.2 KiB text/prs.fallenstein.rst Show Annotation Show as Raw Download as Raw

Søren Løvborg

db: drop length limits on TEXT columns

As of the upgrade to version 1.0 in 3c4b6ddf6735, SQLAlchemy began to
pass TEXT length limits to the database during table creation. Such
limits are however not supported by SQLite, MySQL nor PostgreSQL, and
while SQLite simply ignores it, it is a syntax error in PostgreSQL,
breaking the creation of new PostgreSQL databases. With the lengths
being unused and quite arbitrary, just drop them.

.. _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.