view doc/debugging.txt @ 7093:f72ce883e677

Mitigation for issue2551246 -u opton to roundup-admin The -u option ignores the password and doesn't limit access to the data. Not a huge issue as currently anybody running it must have read access to the tracker home and all the credentials. So they can change the data directly using a db client or read anything they want. But this wasn't documented. Now it is.
author John Rouillard <rouilj@ieee.org>
date Wed, 30 Nov 2022 02:09:16 -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/