Skip to content
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

fix: Upstream API changes in cuDF 24.10 #3309

Closed
wants to merge 4 commits into from

Conversation

martindurant
Copy link
Contributor

No description provided.

@martindurant martindurant changed the title Upstream API changes in cuDF 24.10 fix: Upstream API changes in cuDF 24.10 Nov 19, 2024
Copy link

codecov bot commented Nov 19, 2024

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 82.16%. Comparing base (b749e49) to head (d267b52).
Report is 214 commits behind head on main.

Files with missing lines Patch % Lines
src/awkward/operations/ak_to_cudf.py 0.00% 2 Missing ⚠️
Additional details and impacted files
Files with missing lines Coverage Δ
src/awkward/contents/listoffsetarray.py 81.29% <ø> (-1.57%) ⬇️
src/awkward/operations/ak_to_cudf.py 60.00% <0.00%> (ø)

... and 160 files with indirect coverage changes

Copy link
Member

@jpivarski jpivarski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this need to be coordinated with a cuDF release? If we merge this, would we gain the ability to work with cuDF >= 24.10 and lose the ability to work with cuDF < 24.10?

Also, I should be careful not to merge this PR without resetting the rapidjson submodule.

image

@@ -18,4 +18,4 @@ def to_cudf(
"""
import cudf

return cudf.Series(array.layout._to_cudf(cudf, None, len(array)))
return cudf.Series._from_column(array.layout._to_cudf(cudf, None, len(array)))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This functionality has become private. Is it something we're not supposed to do anymore?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be worth finding the git blame on this, and asking on their repo

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is the PR rapidsai/cudf#16454

@martindurant
Copy link
Contributor Author

I should fix this to check the existence of the class method, so that it works for both new and old versions. I am using this branch for the moment for making my akimbo talk :)

@martindurant
Copy link
Contributor Author

resetting the rapidjson submodule.

did I make it go away?

@jpivarski
Copy link
Member

resetting the rapidjson submodule.

did I make it go away?

Sorry, it's still there in the current diff:

image

@martindurant
Copy link
Contributor Author

How do I undo it? :|

@jpivarski
Copy link
Member

For next time, just delete your fork (locally and on GitHub) and make a new one. (That's how I would do it, just to avoid getting into the weeds of how git submodules work.) It is very unlikely that we'll be changing it again.

For this time, I can recreate the PR, making the same changes as in this PR.

@martindurant
Copy link
Contributor Author

OK, thank you. Perhaps I need to go on a submodule course, if such a thing exists.

@jpivarski
Copy link
Member

I don't know of a better way to do header-only C++ dependencies (with random C++ libraries, not necessarily ones that have a CMake convenience). But other than that, I would rather not use them. They don't work the same way that the rest of git does.

Here are diffs, side by side: if you don't see any differences apart from the rapidjson directory (I don't), then I'll merge it as soon as the tests pass.

This PR: https://github.com/scikit-hep/awkward/pull/3309/files

New PR: https://github.com/scikit-hep/awkward/pull/3328/files

@jpivarski jpivarski closed this Dec 5, 2024
jpivarski added a commit that referenced this pull request Dec 5, 2024
This is an exact copy of PR #3309, which was closed in favor of this one (to avoid issues with the `rapidjson` submodule).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants