-
Notifications
You must be signed in to change notification settings - Fork 609
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: No matching distribution found for opentelemetry-instrumentation-aiohttp-server==0.42b0 #2053
Comments
There was an issue releasing the new version of |
This is also breaking for users (like me) that bring in all instrumentations transitively by depending on opentelemetry-contrib-instrumentations = { version = "0.42b0" } In poetry it fails with:
|
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
|
Any ETA for this issue resolution.?? |
This issue posted last month and still not working. At least to have a workaround before new version release |
Hi Team, |
We fixed it by using the previous version:
After this |
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 |
Confirmed still broken in 0.43b0 for |
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... |
This makes the bootstrap script get the package version directly from pypi instead of from our lists of packages. This makes sure that the packages are actually available for the end user to install. Fixes open-telemetry#2053
This makes the bootstrap script get the package version directly from pypi instead of from our lists of packages. This makes sure that the packages are actually available for the end user to install. Fixes open-telemetry#2053
This makes the bootstrap script get the package version directly from pypi instead of from our lists of packages. This makes sure that the packages are actually available for the end user to install. Fixes open-telemetry#2053
I'm getting the same error for Seems like it's a persistent issue 2 months on |
This was my temporary solution in the project.toml
|
Error is happening on: opentelemetry-distro>=0.43b0
opentelemetry-exporter-otlp>=1.22.0 |
Folks, please see #2053 (comment) this is an issue with PyPI. There is nothing we can do. You can install from Git as mentioned in #2053 (comment) as a workaround |
Wondering if any of you came up with a pip requirements.txt equivalent? I have been trying, without success:
|
We may not need it, I think @lzchen fixed this issue |
Ah the release script fix. 👍 I have an additional change to suggest for the bootstrap script as I've been getting |
This makes the bootstrap script get the package version directly from pypi instead of from our lists of packages. This makes sure that the packages are actually available for the end user to install. Fixes open-telemetry#2053
I think we need to fix the tag. the tag should be
|
Not sure what you are referring to. You would still use |
@lzchen when will it be fixed in 0.44b0 or maybe 0.45b0? |
Above: Until this is addressed, there is no long term solution. Please use the workaround in the meantime. |
Should we expect to have hotfix releases alike 0.43bhotfix or we shouldn't expect such tags as long as the root cause isn't fixed with pypi? |
@ocelotl From my understanding, #2101 is gonna patch this. Is that correct? As in an It looks like pypi/support#3353 won't be addressed any time soon due to how support requests are [not] being handled |
in requirements.txt:
|
This makes the bootstrap script get the package version directly from pypi instead of from our lists of packages. This makes sure that the packages are actually available for the end user to install. Fixes open-telemetry#2053
Another dirty fix for this issue, use it when you actually dont need instrument aiohttp at all.
|
Hi, I'm still having this issue with the new release
|
@ocelotl this still looks broken in 0.46b0
Happens when I have a dependency on 0.46b0
Super easy to reproduce with:
Output:
|
Has changing the name of the package in pyproject.toml been discussed? e.g. from |
Do we have any logs about this conversation? Why changing the name? |
@decko I don't think this has been discussed yet |
This thread itself, it has been suggested in the thread as well, but it hasn't been discussed. The problem it would be trying to solve is the issue in this thread. |
Use for v 0.45b0
|
PyPi issue is solved pypi/support#3353 |
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
The text was updated successfully, but these errors were encountered: