Open brightsparc opened 1 year ago
Hi @brightsparc, thanks for bringing this up. I built the client with geventhttpclient==2.0.8
with the latest Triton version, and I'm still seeing the same issue as mentioned in the PR https://github.com/triton-inference-server/client/pull/185. If you'd like to try, the test we run to verify is L0_https. We have filed a ticket for upgrading the geventhttpclient version in our backlog.
Hi @brightsparc, thanks for bringing this up. I built the client with
geventhttpclient==2.0.8
with the latest Triton version, and I'm still seeing the same issue as mentioned in the PR triton-inference-server/client#185. If you'd like to try, the test we run to verify is L0_https. We have filed a ticket for upgrading the geventhttpclient version in our backlog.
I'd like to help, I didn't see any specific errors in that PR, are you able to share your output.
I took a look at Testing Triton, but wasn't able to build the model repo on my local mac m1, will I require a GPU for this?
Yes, I believe it requires GPU for TensorRT models. However, the model used in L0_https
test can be simply copied from https://github.com/triton-inference-server/server/tree/main/docs/examples/model_repository/simple
. For reference, this is what we do to create the QA container: https://github.com/triton-inference-server/server/blob/main/Dockerfile.QA#L117-L118.
Is there a timeline on updating this geventhttpclient
dependency?
I'm hitting a conflict with the locust
load-testing package, the latest versions of which require geventhttpclient (>=2.0.11)
. This is a bit surprising as some Triton docs recommend this tool.
Alternatively, can I avoid needing geventhttpclient
for tritonclient
? While I do use tritonclient
to make HTTP calls, I only use the asyncio client, not the gevent one.
Is there any update? Currently can't use the regular http client, only the aio one.
Description PR 185 pinned
geventhttpclient==2.0.2
due to a potential change in ssl_context_factory handling.The geventhttpclient releases seem to indicate that there shouldn't be any breaking changes for the handling of
create_default_ssl_context
in version 2.0.8I've validated when upgrading to
geventhttpclient==2.0.8
I am able to make requests to http and grpc endpoints with the tritonclient when passingssl=True
Triton Information What version of Triton are you using?
2.32.0
Are you using the Triton container or did you build it yourself?
Triton container
To Reproduce The following code when run will return
SSLZeroReturnError
when host is using letsencrypt generated cert.Following is the full stack trace:
Expected behavior The expected response, and the one received when we upgrade to
2.0.8
is: