[X] I believe this is a new bug in the Pinecone Python Client
[X] I have searched the existing issues, and I could not find an existing issue for this bug
Current Behavior
Running into the following traceback when trying to embed vectors into pinecone index. Note that this doesn't happen all the time but I am seeing this almost daily in production.
See the full traceback below:
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/control/pinecone.py", line 298, in list_indexes
response = self.index_api.list_indexes()
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api_client.py", line 771, in __call__
return self.callable(self, *args, **kwargs)
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api/manage_indexes_api.py", line 1099, in __list_indexes
return self.call_with_http_info(**kwargs)
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api_client.py", line 833, in call_with_http_info
return self.api_client.call_api(
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api_client.py", line 408, in call_api
return self.__call_api(resource_path, method,
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api_client.py", line 195, in __call_api
response_data = self.request(
File "/home/ubuntu/env/lib/python3.10/site-packages/pinecone/core/client/api_client.py", line 434, in request
File "/home/ubuntu/env/lib/python3.10/site-packages/urllib3/util/retry.py", line 592, in increment
raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='api.pinecone.io', port=443): Max retries exceeded with url: /indexes (Caused by SSLError(SSLEOFError(8, '[SSL: UNEXPECTED_EOF_WHILE_READING] EOF occurred in violation of protocol (_ssl.c:1007)')))
Expected Behavior
It should not fail ideally.
Steps To Reproduce
Steps to reproduce:
Init client
Embed documents and try to add it (Note that this will work most of the times but will fail sporadically)
Is this a new bug in the Pinecone Python client?
Current Behavior
Running into the following traceback when trying to embed vectors into pinecone index. Note that this doesn't happen all the time but I am seeing this almost daily in production.
See the full traceback below:
Expected Behavior
It should not fail ideally.
Steps To Reproduce
Steps to reproduce:
Relevant log output
No response
Environment
Additional Context
No response