qrscu traceback / stack trace not visible in openrem_qr.log
qrscu tracebacks seem to be “swallowed” by celery, making debugging hard. It would perhaps be helpful if tracebacks would be added to the openrem_qr.log automatically.
Comments (6)
-
reporter -
Cool. I’ll take a look later. Thanks for all your work today!
Have you got a reference for where you got this method from?
-
reporter Sorry forgot to mention the sources:
https://stackoverflow.com/questions/16658371/how-to-log-exceptions-occurring-in-a-django-celery-task
https://gist.github.com/darklow/c70a8d1147f05be877c3 -
HI @Tim de Wit - this looks like a sensible thing to do. My only reservation is that I don’t recall being aware that I was missing anything in the current setup!
Can you put a PR together please?
-
reporter Enable logging of stack traces inside qrscu Celery tasks. Refs
#806.→ <<cset 2a82347a4d60>>
-
- changed status to wontfix
Celery no longer in use, and additional QR feedback now incorporated into 1.0, so marking as wontfix.
- Log in to comment
The above seems to be possible by adding the following code to qrscu.py:
adding additional argument to the @shared_task decorators:
Happy to commit these modifications if you think it’s useful… just let me know.