Upgrade WORKSPACE python packages for python3.8 support

[Code0x58]

This upgrades a few python packages. One benefit is that infrastructure/tests work on python3.9 (due to upgrading pex to a version that says it can be installed in python <=3.9) so will fix the issue seen in #3638

[nicknezis]

Looks good. What else is needed to remove from draft status?

[joshfischer1108]

@Code0x58 What do we need to do to pick up work on this branch? Anything I can help with?

[Code0x58]

I think with these changes the python version in Travis blows up, or image (tested via ./scripts/release/build-images --all) having versions that blow up during the build.

I can't recall what specifically required a change from 3.6 to something higher - probably just the newer libraries that work with 3.9.

One path forward is to upgrade all the python versions installed in the container images+CI (Travis + Ubuntu vagrant manifests) to some minimum version - you could use pyenv in the Vagrant machine to find what the lowest working version is. This would be a bit of a pain due to the multiple runtimes required to use Heron, so can't just use pre-existing base images (I think the JRE may be the first class citizen for that in the images). It's not a particularly appealing change, especially considering it may force python tennants to try upgrading their code+dependencies, but it's probably a reasonable thing to do without reconsidering the whole architecture or trying stick with Python 3.6-3.8 only.

[nwangtw]

I am wondering which module uses more libraries? It might be ideal to minimize the use of extra libraries considering the compatibility issues with Python.

…

On Wed, Feb 3, 2021 at 6:08 PM Oliver Bristow ***@***.***> wrote: I think with these changes the python version in Travis blows up, or image (tested via ./scripts/release/build-images --all) having versions that blow up during the build. I can't recall what specifically required a change from 3.6 to something higher - probably just the newer libraries that work with 3.9. One path forward is to upgrade all the python versions installed in the container images+CI (Travis + Ubuntu vagrant manifests) to some minimum version - you could use pyenv in the Vagrant machine to find what the lowest working version is. This would be a bit of a pain due to the multiple runtimes required to use Heron, so can't just use pre-existing base images (I think the JRE may be the first class citizen for that in the images). It's not a particularly appealing change, especially considering it may force python tennants to try upgrading their code+dependencies, but it's probably a reasonable thing to do without reconsidering the whole architecture or trying stick with Python 3.6-3.8 only. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#3646 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQPBH65RSR76W5H75LRT6DS5H6RTANCNFSM4USEOSQQ> .

[nicknezis]

#3642 Code was integrated into this PR.

Tracker Behavior changes:

• replace / → /topologies redirect with (OpenAPI on ReDoc) documentation
• deprecate executiontime and always return 0.0 for it in the response envelope - this could probably be put back in, but I don't think it's worth it
• inbound requests aren't terminated if they take over 120s. At the moment, every outbound request has a 5s limit (due to httpx default) so I wouldn't expect the timeout to be needed (even in metrics queries which may transform data). A replacement timeout could be added in if necessary.