notifications-api

mirror of https://github.com/GSA/notifications-api.git synced 2025-12-20 15:31:15 -05:00

Files

David McDonald fae7e917b5 Fix logging line to include response context

We have been getting log lines of the following:

`API POST request on
https://api.notifications.service.gov.uk/notifications/sms/mmg failed
with None`

It's not clear what error caused the request to fail because the value
of `api_error.response` is always `None`.

There appears to be something wrong with this logging.
`raise_for_status` will raise an `HTTPError`, so then there should be no
reason to then pass that error into another `HTTPError` (which is
causing the response to be lost).

We can instead simply catch the `HTTPError` and log it's status
code.

This might not be perfect, but it's definitely an improvement and should
give us some more context about why these requests occasionally fail.

2020-12-21 14:39:10 +00:00

__init__.py

…

broadcast_message_tasks.py

Remove unused args from cancel broadcast call in tasks

2020-12-14 11:31:05 +00:00

celery.py

dd sqlalchemy connection metrics for celery tasks

2020-06-12 14:52:22 +01:00

letters_pdf_tasks.py

return just the columns we need for collating letters

2020-10-23 20:01:18 +01:00