Prodigy 1.18.x missing from download.prodi.gy

1

Hey there - I was just wondering if something happened to the prodigy download website? I used to be able to get 1.18.x but now I don't see any releases after 1.12.

image

Fairly certain we're up to date, so before I sent a special email, just wanted to check.

2

I've been doing some maintenance on it so there could indeed be a problem. Sorry about this -- I'll look into it for you now.

1 Like
3

You should have access to 1.18.2 again. There may be some more users affected by this -- I'm still working out how some of the license periods got messed up in the migration. It should all be fixed shortly though. None of the order data is missing, it's just some record linkage problems.

1 Like
4

We're missing 1.14.14. Breaks our CI - this shouldn't happen!

5

Confirmed visible. Thanks!

6

@simon.gurcke Yes I'm very sorry about this. It's fixed now --- I just checked with your license key and it correctly downloads v1.14.4.

1 Like
7

@honnibal This is still broken for us. Could you please look into it again.

#10 22.27   - Installing prodigy (1.14.14)
#10 23.29 
#10 23.29   RuntimeError
#10 23.29 
#10 23.29   Unable to find installation candidates for prodigy (1.14.14)
#10 23.29 
#10 23.29   at /opt/poetry/lib/python3.12/site-packages/poetry/installation/chooser.py:86 in choose_for
#10 23.30        82│ 
#10 23.30        83│             links.append(link)
#10 23.30        84│ 
#10 23.30        85│         if not links:
#10 23.30     →  86│             raise RuntimeError(f"Unable to find installation candidates for {package}")
#10 23.30        87│ 
#10 23.30        88│         # Get the best link
#10 23.30        89│         chosen = max(links, key=lambda link: self._sort_key(package, link))
#10 23.30        90│ 
#10 23.30 
#10 23.30 Cannot install prodigy.
#10 23.30 
#10 ERROR: process "/bin/bash -o pipefail -c poetry config http-basic.fury $FURY_DEPLOY_TOKEN NOPASS &&     poetry config http-basic.prodigy $PRODIGY_LICENSE_KEY NOPASS &&     poetry install --with prodigy,ml --without dev --no-root --no-interaction --no-ansi &&     rm -rf $HOME/.cache/pypoetry" did not complete successfully: exit code: 1
------
 > [jobs 4/9] RUN poetry config http-basic.fury xxx NOPASS &&     poetry config http-basic.prodigy xxx NOPASS &&     poetry install --with prodigy,ml --without dev --no-root --no-interaction --no-ansi &&     rm -rf $HOME/.cache/pypoetry:
23.30        84│ 
23.30        85│         if not links:
23.30     →  86│             raise RuntimeError(f"Unable to find installation candidates for {package}")
23.30        87│ 
23.30        88│         # Get the best link
23.30        89│         chosen = max(links, key=lambda link: self._sort_key(package, link))
23.30        90│ 
23.30 
23.30 Cannot install prodigy.
23.30
8

Sorry you're still having trouble. It could be down to one of two things as far as I can see.

  1. Which license key are you using? I have two orders from genesiscare: a personal license 12 July 2021, and a company pack 26 Oct 2022. I've tested the company pack and I correctly downloaded 1.14.14.
  2. What Python version are you using? Our older Prodigy versions were provided as binary wheels, and there's support up to Python 3.11 for your version range. Support for ARM architectures is limited however. If you try to install with an incompatible Python/arch combination, it won't be able to find a matching Prodigy file for you. Current versions of Prodigy are provided as an uncompiled installation with source code access, which is compatible across Python versions.
9

This is the company license, Python 3.12 and amd64 arch.

We haven't made any changes recently that could've broken this. The project has been using Python 3.12 for a long time and was able to install Prodigy before.

I've just checked again and we're still getting "Unable to find installation candidates for prodigy (1.14.14)".

We're using Poetry and I see there's another user with what seems to be the same issue:

Maybe this is related?

Note: This issue has a big impact. For us, Prodigy is a dependency in a large legacy codebase. We're unable to merge PRs and create releases, ultimately affecting our own customers who are waiting for features and bug fixes. Please treat this with urgency.

I've been doing some maintenance on it so there could indeed be a problem.

This statement sounds like you're tinkering with production systems that your customers rely on without appropriate quality controls. I really hope you invest in better processes and this doesn't happen again.

Do you have a backup you could roll back to?

10

Could you try installing via --find-links instead? I believe the fault may be with the way the page is served for the --extra-index-url installation method with pip, which I think Poetry uses.

I do regret the fault, but as context we're a company of three people, and your company is not paying any ongoing fee for this service. We therefore have practical considerations about what processes we use to maintain it.

Prodigy comes with a lifetime license and 12 months of free updates. We provide a download service as a convenience to ship the software to people, and we continue to provide access to users whose update period has expired as a courtesy. If you have a large legacy system depending on this download service, you could consider migrating to your own PyPi service.

11

I've now tested the --extra-index-url API as well with your license, and confirmed it works.