Open lithomas1 opened 3 days ago
Describe the bug A clear and concise description of what the bug is.
libcudf hangs in replace multiple when the targets column contains an empty string.
Steps/Code to reproduce bug Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly.
Using pylibcudf,
import pyarrow as pa import cudf._lib.pylibcudf as plc input_array = pa.array([ "a", "b", "c", "d", "e", "f", "g", "h", ]) data = pa.array([ "AbC", "de", "FGHI", "j", "kLm", "nOPq", "", "RsT", ]) print('hang starts now!') plc.strings.replace.replace_multiple( plc.interop.from_arrow(input_array), plc.interop.from_arrow(data), plc.interop.from_arrow(input_array) )
Expected behavior A clear and concise description of what you expected to happen.
Environment overview (please complete the following information)
docker pull
docker run
Environment details Please run and paste the output of the cudf/print_env.sh script here, to gather any other relevant environment details
cudf/print_env.sh
Additional context Add any other context about the problem here.
Backtrace (sorry, I didn't have the time to figure out how to compile libcudf in debug mode, but hopefully this helps)
I got it by pressing ctrl+c in gdb after "hang starts now" is printed
Empty targets for cudf::strings::replace_multiple are not supported. I'll open a PR to fix the hang and update the doxygen.
cudf::strings::replace_multiple
Describe the bug A clear and concise description of what the bug is.
libcudf hangs in replace multiple when the targets column contains an empty string.
Steps/Code to reproduce bug Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly.
Using pylibcudf,
Expected behavior A clear and concise description of what you expected to happen.
Environment overview (please complete the following information)
docker pull
&docker run
commands usedEnvironment details Please run and paste the output of the
cudf/print_env.sh
script here, to gather any other relevant environment detailsAdditional context Add any other context about the problem here.
Backtrace (sorry, I didn't have the time to figure out how to compile libcudf in debug mode, but hopefully this helps)
I got it by pressing ctrl+c in gdb after "hang starts now" is printed