cuml
cuml copied to clipboard
[BUG] Exception when running a simple StandardScaler example using a container without dask_cudf
Describe the bug
I'm using a singularity RAPIDS container and I'm getting a weird exception when I run the StandardScaler
example from CuML doc.
Steps/Code to reproduce bug
Use any clean environment without dask_cudf and try the StandardScaler
example from CuML doc.
Expected behavior The simple code should be executed without any issue.
Environment details (please complete the following information):
- Environment location: Singularity Container (from docker bootstrap)
- Linux Distro/Architecture: CentOS 8
- GPU Model/Driver: 2x NVIDIA A100
- CUDA: 11.5
- Method of cuDF & cuML install: conda
Additional Info I've already opened a PR to fix this issue #4747
This is curious because I'm not using dask_cudf structures in my example, but the error appears (see PR for further details).
The packages related to dask_cudf is installed, but it has a bug (which was fixed in recent versions).
Traceback (most recent call last):
File "scaler_test.py", line 3, in <module>
import dask_cudf
File "/opt/conda/envs/rapids/lib/python3.8/site-packages/dask_cudf/__init__.py", line 6, in <module>
from . import backends
File "/opt/conda/envs/rapids/lib/python3.8/site-packages/dask_cudf/backends.py", line 21, in <module>
from dask.dataframe.utils import (
ImportError: cannot import name 'is_arraylike' from 'dask.dataframe.utils' (/opt/conda/envs/rapids/lib/python3.8/site-packages/dask/dataframe/utils.py)
The function is_arraylike
is defined inside dask.utils
and, again, it was fixed.
The point is... an external error is causing an import failure which affects an example that does not use dask_cudf. The PR should cover this specific case, I guess.
This issue has been labeled inactive-30d
due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d
if there is no activity in the next 60 days.
This issue has been labeled inactive-90d
due to no recent activity in the past 90 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.