[Snyk] Security upgrade tensorflow from 1.13.1 to 1.15.4

[snyk-bot]

Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.

Changes included in this PR

• Changes to the following files to upgrade the vulnerable dependencies to a fixed version:
  • requirements-databricks.txt

⚠️ Warning

statsmodels 0.6.1 requires patsy, which is not installed.
requests 2.20.1 has requirement idna<2.8,>=2.5, but you have idna 2.10.
pyarrow 0.13.0 has requirement numpy>=1.14, but you have numpy 1.11.1.

Vulnerabilities that will be fixed

By pinning:

Severity	Priority Score (*)	Issue	Upgrade	Breaking Change	Exploit Maturity
	591/1000 Why? Recently disclosed, Has a fix available, CVSS 5.9	NULL Pointer Dereference SNYK-PYTHON-TENSORFLOW-1013553	tensorflow: 1.13.1 -> 1.15.4	No	No Known Exploit
	536/1000 Why? Recently disclosed, Has a fix available, CVSS 4.8	Out-of-Bounds SNYK-PYTHON-TENSORFLOW-1013583	tensorflow: 1.13.1 -> 1.15.4	No	No Known Exploit
	721/1000 Why? Recently disclosed, Has a fix available, CVSS 8.5	Heap-based Buffer Overflow SNYK-PYTHON-TENSORFLOW-1013602	tensorflow: 1.13.1 -> 1.15.4	No	No Known Exploit
	621/1000 Why? Recently disclosed, Has a fix available, CVSS 6.5	Improper Input Validation SNYK-PYTHON-TENSORFLOW-1013605	tensorflow: 1.13.1 -> 1.15.4	No	No Known Exploit
	746/1000 Why? Recently disclosed, Has a fix available, CVSS 9	Denial of Service (DoS) SNYK-PYTHON-TENSORFLOW-1013618	tensorflow: 1.13.1 -> 1.15.4	No	No Known Exploit

(*) Note that the real score may have changed since the PR was raised.

Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the effected dependencies could be upgraded.

Check the changes in this PR to ensure they won't cause issues with your project.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report

🛠 Adjust project settings

📚 Read more about Snyk's upgrade and patch logic

[coveralls]

Coverage remained the same at 95.533% when pulling 27818dd on snyk-fix-3172f834cbd6683504495e3849411933 into 247410c on master.