requirements-app.txt

# Run `make freeze-requirements` to update requirements.txt
# with package version changes made in requirements-app.txt

ago==0.0.92
Flask==1.0.2
Flask-WTF==0.14.2
Flask-Login==0.4.1

blinker==1.4
pyexcel==0.5.9.1
pyexcel-io==0.5.9.1
pyexcel-xls==0.5.8
pyexcel-xlsx==0.5.6
pyexcel-ods3==0.5.2
pytz==2018.5
gunicorn==19.7.1  # >19.8 stops eventlet workers after a timeout
whitenoise==4.1  #manages static assets
eventlet==0.24.1
notifications-python-client==5.2.0

# PaaS
awscli-cwlogs>=1.4,<1.5
awscli==1.15.82
botocore<1.11.0


# Putting upgrade on hold due to v1.0.0 using sha512 instead of sha1 by default
itsdangerous==0.24  # pyup: <1.0.0

git+https://github.com/alphagov/notifications-utils.git@30.5.6#egg=notifications-utils==30.5.6
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00			# Run `make freeze-requirements` to update requirements.txt
			`# with package version changes made in requirements-app.txt`

			`ago==0.0.92`
			`Flask==1.0.2`
			`Flask-WTF==0.14.2`
			`Flask-Login==0.4.1`

			`blinker==1.4`
Update pyexcel to 0.5.9.1 0.5.9 seems to have disappeared and is causing tests to fail on Jenkins. https://github.com/pyexcel/pyexcel/compare/v0.5.9...v0.5.9.1 2018-09-03 13:51:18 +01:00			`pyexcel==0.5.9.1`
Update pyexcel-io from 0.5.9 to 0.5.9.1 2018-09-03 09:55:48 +01:00			`pyexcel-io==0.5.9.1`
Update pyexcel-xls from 0.5.7 to 0.5.8 2018-09-03 09:56:45 +01:00			`pyexcel-xls==0.5.8`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00			`pyexcel-xlsx==0.5.6`
			`pyexcel-ods3==0.5.2`
			`pytz==2018.5`
Stop gunicorn from terminating eventlet workers on timeout According to gunicorn `timeout` docs, async workers shouldn't be terminated after the request time exceeds the specified timeout as long as the worker process is still communicating. This makes sense for async workers since they generally don't block other requests from processing. This is the behaviour we've seen on notifications-api - requests can sometimes take much longer than the default 30 second timeout and still succeed. For the admin app however gunicorn has been shutting down workers after 30s with `[CRITICAL] WORKER TIMEOUT`. This results in a 502 response from the admin app. Most of these requests fail because the underlying requests to the api is taking longer than 30 seconds, however we haven't seen this in the logs originally since unlike the admin app, api requests succeed (even though their response is no longer needed). This seems like a bug in newer versions of gunicorn, downgrading it to the version that the api is currently using solves the problem by allowing admin requests to take longer than 30 seconds. (Tested by trying requests with a `time.sleep(30)` locally). It's not clear what exactly the bug in gunicorn is, but this also potentially unblocks eventlet workers and allows them to process more than one request at a time. 2018-09-18 11:25:42 +01:00			`gunicorn==19.7.1 # >19.8 stops eventlet workers after a timeout`
Update whitenoise from 4.0 to 4.1 2018-09-19 17:17:32 +01:00			`whitenoise==4.1 #manages static assets`
Update eventlet from 0.22.1 to 0.24.1 2018-08-20 11:46:28 +01:00			`eventlet==0.24.1`
Update notifications-python-client from 5.1.0 to 5.2.0 2018-09-25 12:13:16 +01:00			`notifications-python-client==5.2.0`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
			`# PaaS`
			`awscli-cwlogs>=1.4,<1.5`
update jobs to take into account first class 2018-09-28 17:08:28 +01:00			`awscli==1.15.82`
			`botocore<1.11.0`
Pin all requirements in requirements.txt The list of top-level dependencies is moved to requirements-app.txt, which is used by `make freeze-requirements` to generate the full list of requirements in requirements.txt. (See alphagov/notifications-api#1938 for details.) 2018-07-10 15:16:14 +01:00
Update notifications-utils to 30.5.6 This brings in the change to email validation which removes obscure white space from email addresses. 2018-10-29 10:21:04 +00:00
			`# Putting upgrade on hold due to v1.0.0 using sha512 instead of sha1 by default`
			`itsdangerous==0.24 # pyup: <1.0.0`

			`git+https://github.com/alphagov/notifications-utils.git@30.5.6#egg=notifications-utils==30.5.6`