Vibhu Jawa

Thanks for triaging and raising this @ChrisJar . I can confirm that i can reproduce this on my end too. Smaller minimal example for anyone interested. ```python import numpy as...

CC: @rjzamora , @galipremsagar

@ChrisJar , Can you raise an issue on `dask-sql` too just as it will be hard for users to work-around from that world as there the merge can be present...

@rjzamora , I agree that "general" type-casting rules are pretty vague so having a general agree-able behavior will be impossible. > What type of dtype mismatch we should worry about...

> Is it common to merge on floating-point columns? I dont this its common but as you say users can do that accidentally in workflows . A common example i...

@MaartenGr , Thanks a lot. Its great to learn that now it is possible to use different models for `HDBSCAN` and `UMAP.` From a benchmark perspective on a workflow we...

Thanks for the ping as well as the work you have done on the library @MaartenGr . > which is a GPU-accelerated version of BERTopic using RAPIDS to primarily speed...

**MRE:** EDIT: Cleaned up MRE to be easier to understand. ```python import cudf import cugraph import numpy as np df = cudf.DataFrame({'source':[1,1], 'destination':[2,2], 'eids':[0,1] }) df = df.astype(np.int32) G =...

> ```python > import cudf > import cugraph > import numpy as np > > df = cudf.DataFrame({'source':[1,1], > 'destination':[2,2], > 'eids':[0,1] > }) > df = df.astype(np.int32) > >...

> Ok, so you want the current behavior, but with the `is_edge_ids` flag specifying whether the weights are edge ids rather than always assuming they are, correct? Yup. Thats my...