Bugs can behave as application crashes or as various misbehavior. You are welcome to collect info on any such issue and submit it to the issue tracker.
Turning on debug mode will make the exceptions show in the web browser. This is useful to debug issues in the web interface, but not suitable for a production environment because it has performance consequences and might leak private data.
In a production environment, use
ADMINS to receive e-mails containing error
reports, or configure error collection using a third-party service.
Weblate can produce detailed logs of what is going on in the background.
In the default configuration it uses syslog and that makes the log appear either in
/var/log/syslog (depending on your syslog
The Celery process (see Background tasks using Celery) usually produces its own logs as well.
The example system-wide setups logs to several files under
Docker containers log to their output (as per usual in the Docker world), so
you can look at the logs using
Sample configuration contains
Not processing background tasks
A lot of things are done in the background by Celery workers. If things like sending out e-mails or component removal does not work, there might a related issue.
Things to check in that case:
Check that the Celery process is running, see Background tasks using Celery
Check the Celery queue status, either in Ndërfaqe administrimi, or using
Look in the Celery logs for errors (see Regjistra Weblate-i)
Not receiving e-mails from Weblate
You can verify whether outgoing e-mail is working correctly by using the
sendtestemail management command (see Invoking management commands
for instructions on how to invoke it in different environments) or by using
Ndërfaqe administrimi under the Tools tab.
These send e-mails directly, so this verifies that your SMTP configuration is correct (see Formësim i email-eve që dërgohen). Most of the e-mails from Weblate are however sent in the background and there might be some issues with Celery involved as well, please see Not processing background tasks for debugging that.
Analyzing application crashes
In case the application crashes, it is useful to collect as much info about the crash as possible. This can be achieved by using third-party services which can collect such info automatically. You can find info on how to set this up in Collecting error reports.
Lots of tasks are offloaded to Celery for background processing. Failures are not shown in the user interface, but appear in the Celery logs. Configuring Collecting error reports helps you to notice such failures easier.
In case Weblate performs badly in some scenario, please collect the relevant logs showing the issue, and anything that might help figuring out where the code might be improved.
In case some requests take too long without any indication, you might want to install dogslow along with Collecting error reports and get pinpointed and detailed tracebacks in the error collection tool.