-
Notifications
You must be signed in to change notification settings - Fork 94
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
cannot install dask-cuda without pulling in vulnerable dask #796
Comments
In this case we'd recommend either installing from source or installing from our nightly package channel:
Note we will have officially released version of dask-cuda 21.12 early December. |
neither are available options I'm afraid would it be possible to backport the patch as a post-release? |
It's unlikely we can backport that patch across the all of RAPIDS. I will talk to folks about what we can do here. If possible, can you elaborate on why upgrading is not a viable option ? |
our security team requires us to only install packages from pypi so we do not have access to conda nor git during our installation process |
There are prereleases on PyPI. Can you use those? |
Using them isn't possible because RAPIDS 21.10 pinned exactly to |
You said your organization can only install from PyPI so your only need is dask-cuda, is that correct ? cuDF and much of the RAPIDS ecosystem is not pip installable |
yeah we don't use those at the moment, only dask-cuda |
We do upload pre-releases as @jakirkham mentioned: |
This issue has been labeled |
I don't think we're able to change that for RAPIDS 21.10 or older, so the recommendation now that 21.12 is out is to upgrade. Therefore I'm closing this, but please reopen if there's a strong reason for which 21.12 can't be used. |
the currently released version of dask-cuda pins
dask==2021.9.1
which has a critical CVE: https://nvd.nist.gov/vuln/detail/CVE-2021-42343currently an install forces this:
it looks like #742 fixes the pin but has not been released / backported
The text was updated successfully, but these errors were encountered: