view doc/debugging.txt @ 6589:5ce396880899

Add error templates for 400 and label each item optional Added documenttion on adding a _generic.400.html template which can be used to display errors in FTS query syntax. It can include the chrome supplied by page.html which makes navigating etc. easier. Also labeled each section title in the current release optional as none of them are required upgrades. If we add a required step that will break a tracker if not done, it should be labeled required and put at the top of the upgrading section.
author John Rouillard <rouilj@ieee.org>
date Mon, 24 Jan 2022 21:16:30 -0500
parents a635a60ffb84
children
line wrap: on
line source

Debugging Aids
--------------

Try turning on logging of DEBUG level messages. This may be done a number
of ways, depending on what it is you're testing:

1. If you're testing the database unit tests, then set the environment
   variable ``LOGGING_LEVEL=DEBUG``. This may be done like so:

    LOGGING_LEVEL=DEBUG python -m pytest test/

   This variable replaces the older HYPERDBDEBUG environment var.

2. If you're testing a particular tracker, then set the logging level in
   your tracker's ``config.ini``.

SENDMAILDEBUG
=============

Set to a filename and roundup will write each email message
that it sends to that file instead to the internet. 
This environment variable is independent of the python -O flag.


Roundup Issue Tracker: http://roundup-tracker.org/