opentelemetry-python-contrib
opentelemetry-python-contrib copied to clipboard
ERROR: No matching distribution found for opentelemetry-instrumentation-aiohttp-server==0.42b0
Python Version - 3.8
Steps to reproduce Using 'opentelemetry-bootstrap -a install' Command to Install the Dependencies for Auto Instrumentation.
What is the expected behavior? package : opentelemetry-instrumentation-aiohttp-server==0.42b0 should be downloaded from pypi
What is the actual behavior? ERROR: No matching distribution found for opentelemetry-instrumentation-aiohttp-server==0.42b0
There was an issue releasing the new version of opentelemetry-instrumentation-aiohttp-server==0.42b0
, we are working on it to get it resolved.
This is also breaking for users (like me) that bring in all instrumentations transitively by depending on opentelemetry-contrib-instrumentations
. For example, this is broken (poetry example):
opentelemetry-contrib-instrumentations = { version = "0.42b0" }
In poetry it fails with:
Because opentelemetry-contrib-instrumentations (0.42b0) depends on opentelemetry-instrumentation-aiohttp-server (0.42b0) which doesn't match any versions, opentelemetry-contrib-instrumentations is forbidden.
We are also affected by this. We've removed opentelemetry instrumention temporarily as a workaround, but this is not an option for everybody of course.
any updates on this issue?
Receiving the same behaviour with 3.10.3
$ opentelemetry-bootstrap -a install
ERROR: Could not find a version that satisfies the requirement opentelemetry-instrumentation-aiohttp-server==0.42b0 (from versions: none)
ERROR: No matching distribution found for opentelemetry-instrumentation-aiohttp-server==0.42b0
There was an issue releasing the new version of
opentelemetry-instrumentation-aiohttp-server==0.42b0
, we are working on it to get it resolved.
Any ETA for this issue resolution.?? As we are forced to disable the instrumentation.
This issue posted last month and still not working. At least to have a workaround before new version release
There was an issue releasing the new version of
opentelemetry-instrumentation-aiohttp-server==0.42b0
, we are working on it to get it resolved.
Hi Team, Kindly help here with resolution. We need to disable instrumentation for all affected services.
We fixed it by using the previous version:
pip install opentelemetry-distro==0.41b0 opentelemetry-exporter-otlp==1.20.0
After this opentelemetry-bootstrap --action install
works fine.
The above fix works- but would be great to have a complete fix and get back to reliable python install.
In 0.43b0 I'm seeing this same error but with the opentelemetry-instrumentation-aws-lambda==0.43b0
package and possibly others.
Confirmed still broken in 0.43b0 for opentelemetry-instrumentation-aiohttp-server
We have this issue because we can't release this package anymore to PyPi, we have reported it here already.
I'm investigating a workaround for the time being, will report back here...
Someone forgot to add the folder to the package 0.43b0
I was trying the workaround with the pyproject.tolm specification , but then i noticed that. Maybe the solution would be getting the commit that have the correct version
opentelemetry-instrumentation-aiohttp-server= {git = "https://github.com/open-telemetry/opentelemetry-python-contrib/",subdirectory="instrumentation/opentelemetry-instrumentation-aiohttp-server" ,tag = "v0.43b0"}
I'm getting the same error for opentelemetry-instrumentation-aiohttp-server==0.43b0
when running poetry run opentelemetry-bootstrap -a install
Seems like it's a persistent issue 2 months on
This was my temporary solution in the project.toml
opentelemetry-exporter-otlp = "^1.20.0"
opentelemetry-distro = "^0.41b0"
opentelemetry-exporter-jaeger = "^1.21.0"
Error is happening on:
opentelemetry-distro>=0.43b0
opentelemetry-exporter-otlp>=1.22.0
Folks, please see https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2053#issuecomment-1865032194 this is an issue with PyPI. There is nothing we can do. You can install from Git as mentioned in https://github.com/open-telemetry/opentelemetry-python-contrib/issues/2053#issuecomment-1879799993 as a workaround
I was trying the workaround with the pyproject.tolm specification , but then i noticed that. Maybe the solution would be getting the commit that have the correct version
opentelemetry-instrumentation-aiohttp-server= {git = "https://github.com/open-telemetry/opentelemetry-python-contrib/",subdirectory="instrumentation/opentelemetry-instrumentation-aiohttp-server" ,tag = "v0.43b0"}
Wondering if any of you came up with a pip requirements.txt equivalent? I have been trying, without success:
git+https://github.com/open-telemetry/[email protected]#subdirectory=instrumentation/opentelemetry-instrumentation-aiohttp-server
I was trying the workaround with the pyproject.tolm specification , but then i noticed that. Maybe the solution would be getting the commit that have the correct version
opentelemetry-instrumentation-aiohttp-server= {git = "https://github.com/open-telemetry/opentelemetry-python-contrib/",subdirectory="instrumentation/opentelemetry-instrumentation-aiohttp-server" ,tag = "v0.43b0"}
Wondering if any of you came up with a pip requirements.txt equivalent? I have been trying, without success:
git+https://github.com/open-telemetry/[email protected]#subdirectory=instrumentation/opentelemetry-instrumentation-aiohttp-server
yeah I've been trying to figure that out and I don't see that as a solution anywhere here.
could someone just write the pip install command to run, and we can put all this behind us. I'm about to just take the folder out and make it into its own pypi
Thanks @naisanzaa this is real issue. It looks like the subdirectory was deleted in the git repo at the release tag as well. @ocelotl do you remember the context of https://github.com/open-telemetry/opentelemetry-python-contrib/commit/8c9df875e4bdbde95f22d874ee5be53ec7de3306?
@aabmass
I believe we removed them manually from the commit since it was failing the release build. The build fails as soon as an error occurs and the packages that need to be released after the order are ignored and not released properly. The temporary solution should just be ignoring those two specific packages from our release script, instead of removing them manually from the release commit.
Thanks @naisanzaa this is real issue. It looks like the subdirectory was deleted in the git repo at the release tag as well. @ocelotl do you remember the context of https://github.com/open-telemetry/opentelemetry-python-contrib/commit/8c9df875e4bdbde95f22d874ee5be53ec7de3306?
Any chance to make an opentelemetry-python-contrib-hotfix pypi repo. And just update the scripts back once this 3 month ongoing problem fixes itself?
@lzchen to @naisanzaa's point, can we create a public git tag like aiohttp-server-v0.43b0
at the parent commit (68bea0c10806056d4578446f8cb2167508094a21) so people can install it?
@lzchen to @naisanzaa's point, can we create a public git tag like
aiohttp-server-v0.43b0
at the parent commit (68bea0c10806056d4578446f8cb2167508094a21) so people can install it?
This needs to be the solution today.
Looking into this...
I have added a new tag: 0.43b0hotfix
. This can be used to install opentelemetry-instrumentation-aiohttp-server
and opentelemetry-resource-detector-container
with the following pip
commands:
pip install git+https://github.com/open-telemetry/[email protected]#subdirectory=instrumentation/opentelemetry-instrumentation-aiohttp-server
pip install git+https://github.com/open-telemetry/[email protected]#subdirectory=resource/opentelemetry-resource-detector-container
Hi @ocelotl , could we also have a 0.44b0hotfix
tag following today's release?