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

Vendor cloudpickle #686

Merged
merged 4 commits into from
Dec 11, 2024
Merged

Vendor cloudpickle #686

merged 4 commits into from
Dec 11, 2024

Conversation

sgillies
Copy link
Collaborator

@sgillies sgillies commented Dec 4, 2024

All code now does from tiledb.cloud._vendor import cloudpickle as tdbcp.

@sgillies sgillies self-assigned this Dec 4, 2024
@sgillies sgillies marked this pull request as ready for review December 4, 2024 16:05
@sgillies sgillies requested a review from ihnorton December 4, 2024 16:09
@sgillies
Copy link
Collaborator Author

sgillies commented Dec 4, 2024

I went through every failing test at 731c846. They are all explained by tiledb.cloud._vendor.cloudpickle not existing on the server side.

@ihnorton what do you think about this approach? Would you prefer vendoring be done any other way?

Copy link
Member

@ihnorton ihnorton left a comment

Choose a reason for hiding this comment

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

This makes sense to me. Other than the minor inline comment, have one question which I'll take offline. Thanks!

@@ -1,6 +1,6 @@
attrs==23.2.0
certifi==2024.2.2
cloudpickle==2.2.1
cloudpickle
Copy link
Member

Choose a reason for hiding this comment

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

Should we remove this?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@ihnorton I did at one point, and then realized that if tests don't pass with cloudpickle 3 in the environment, we have a major problem. I'm inclined to leave it for now.

@sgillies
Copy link
Collaborator Author

sgillies commented Dec 6, 2024

Again, I went through every failing test at 6bc48b5. They are all explained by tiledb.cloud._vendor.cloudpickle not existing on the server side.

Copy link
Member

@ihnorton ihnorton left a comment

Choose a reason for hiding this comment

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

Thanks!

@sgillies sgillies added the enhancement New feature or request label Dec 11, 2024
@sgillies sgillies merged commit 638e6c3 into main Dec 11, 2024
12 of 18 checks passed
@sgillies sgillies deleted the sg/sc-59845/vendor-cloudpickle-take-2 branch December 11, 2024 20:53
spencerseale pushed a commit that referenced this pull request Dec 17, 2024
* Vendor cloudpickle

* Install missing cloudpickle test components

* Add cloudpickle back to CI requirements

Needed by a pickle compatibility test

* In module code, import vendored cloudpickle as tdbcp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants