Closed caniko closed 2 years ago
There's not much actual poetry debug log here to work with.
When I add syndb-cassandra i get version 2.0.1, which appears to be the latest version available.
It sounds like a caching issue, have you tried with --no-cache?
@clintonroy did you use my method to reproduce? Please write in a way that makes it clear that you have read the issue, it looks like you haven't. :pray:
Nevertheless, I should've included a verbose output. Adding this.
--no-cache does not work. I'll add this to the main post, thanks.
your log shows you depending on syndb-cassandra >=2.1.0
, pypi shows that the most recent release of that project - half an hour ago at time of writing - is 2.0.1
.
Not only poetry cannot find version 2.1.0, no-one can.
I made this pyproject.toml
as a dummy during debug. My bad that I added wrong version. You are also answering as if you haven't read the main post. People, make an effort please. I'd prefer help from ~poetry maintainers~ those willing to put in the effort to reproduce the issue.
@dimbleby you need to follow the reproduce guide. Updated the version nevertheless.
Edit: Unfair to discriminate based on rank, apologies for this. Good Sunday.
All the best but I'm out: some people just don't want to be helped.
All the best but I'm out: some people just don't want to be helped.
Lets not degenerate, please. I do want help and actually make poetry better. Just not help from you, who doesn't put in the effort to reproduce the issue (wasting everybody's time), thank you.
Side note first: Please be respectful of people that take some of their time to help you, even if in the end it doesn't fix your issue. Remember that people do that on their free time, like everybody that is involved in this project, and that they don't owe you anything specifically, so please be considerate of that the next time you comment or create an issue, especially if you used a non-reproducible example to begin with that only added to the confusion behind the issue.
Poetry uses PyPI's JSON API to retrieve the available versions, while pip uses the legacy API, so it may at least explain why you notice a different behaviour.
It happened multiple times in the past that the JSON API had a bit of delay before listing newer versions (which seems to not happen, or at a lesser rate, on the legacy API). Not saying this is the cause for sure here, but a possible one.
What may help find the root cause would be to check, next time you reproduce the issue (or right now, if you still have the issue with 2.0.1
), if the latest version of the library you depend on is listed in the JSON API in both:
https://pypi.org/pypi/syndb-cassandra/json
https://pypi.org/pypi/syndb-cassandra/<version>/json
This would help figure out if the issue is related to the JSON API or not.
I think respect goes both ways here. I am fine with a workaround instead of making an issue, I put in effort for the communities benefit too. Either put in the time to reproduce and ask followups or don't bother—you are wasting everybodies time.
It is triggering when someone rebutes your entire issue because of elements unrelated to the issue. Please, let us move forward. I just want to make poetry better.
As mentioned, you can reproduce the issue yourself.
I'll keep it in mind, and keep you posted unless someone else does it before me. Update @mkniewallner days have past still the same issue on the same envrionment that has the previous version in its .lock file.
Closing because of the degeneration.
OK, we can continiue here.
Days go past, and I still don't get the latest when I update, as captured by the reproduce method. None of the replies tried to reproduce the issue, or wasn't explicit about it. I found it fitting because of the beforementioned, and the negativity to move on in a new issue.
Note that I closed it today when this was clear, and not the day of the negativity.
FWIW I am also facing this issue currently with Poetry 1.2.0 when trying to get mypy 0.981 which was just released and can be found on PyPi and via pip, but poetry is not currently picking it up.
I also can see 0.981 at the json endpoints https://pypi.org/pypi/mypy/json and https://pypi.org/pypi/mypy/0.981/json
Attached are the results from those endpoints and the -vvv
output of a poetry update
with mypy
pinned to *
.
This is interestingly some sort of caching issue with PyPI's CDN and the JSON endpoints. Completely removing all caching from the Poetry 1.2.1 tag does not resolve it, and likewise, a clean browser profile still pulls up the old JSON (while curl
does not):
Interestingly, https://github.com/python-poetry/poetry/pull/6081 resolves this by not getting versions from the JSON API anymore (for unrelated reasons mostly relating to upstream technical debt).
Pinging @dstufft to take a look as they have helped investigate Poetry issues from the warehouse side before.
Closing for now as PyPI is tracking the issue upstream, and we've merged use of the Simple API for this -- we no longer get version information from the JSON API.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
[x] I am on the latest Poetry version.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
~[ ] If an exception occurs when executing a command, I executed it again in debug mode (
-vvv
option).~Poetry version: 1.2.0 (installed with pipx)
OS info is on bottom.
pyproject.toml
Issue
poetry fails to resolve latest version on
poetry update
, I recently updated my packagesyndb-cassandra
. This happened both 2 days ago, and now. I am certain that this issue still percists. The issue is at least very similar to #3543.I bumped the version
.toml
file to make sure, I get this:This issue won't occur for you however, follow reproduce guide.
no-cache
flagg has no effect.Reproduce
poetry lock
Bpoetry update
BThis will fail to find the latest package.
pip install -U <package_name>
inside the poetry package env will succeed.Verbose error output
System and OS info