Closed lylejohnson closed 1 year ago
Yes. I ran into the problem described in this issue, which was apparently resolved by this pull request; however, that code has not yet been released.
I'd like for the team to schedule a release of opensearch-py (presumably version 2.3.2) which incorporates this fix.
opensearch-py
I'm not sure what my other options are, other than maybe installing from a patched version of the source?
N/A
Releasing 2.3.2 would help OpenSearch-Benchmark with the following CVE-Risk. Once this has been released, we can switch OSB to use 2.3.2 instead of 2.2.0 (which uses the urllib3 version that has a CVE-Risk)
Is your feature request related to a problem?
Yes. I ran into the problem described in this issue, which was apparently resolved by this pull request; however, that code has not yet been released.
What solution would you like?
I'd like for the team to schedule a release of
opensearch-py
(presumably version 2.3.2) which incorporates this fix.What alternatives have you considered?
I'm not sure what my other options are, other than maybe installing from a patched version of the source?
Do you have any additional context?
N/A