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 ambiguous capsule calls with pybind11 #1887

Merged
merged 3 commits into from
Feb 14, 2024
Merged

Fix ambiguous capsule calls with pybind11 #1887

merged 3 commits into from
Feb 14, 2024

Conversation

robertbindar
Copy link
Contributor

I got multiple errors like this:
error: call of overloaded ‘capsule(std::__shared_ptr<tiledb_subarray_t, __gnu_cxx::_S_atomic>::element_type*, const char [9], std::nullptr_t)’ is ambiguous
when building fresh with latest pybind on ubuntu22, m6id.4xlarge ec2 machine.

Not sure this is the correct fix, just fixed all the errors to get myself a successful build and thought effort shouldn't go to waste in case it's the correct approach.

@nguyenv
Copy link
Collaborator

nguyenv commented Jan 12, 2024

This looks correct to me, but I swear we already made these changes before to fix these errors. Maybe it was in different files, or maybe even in the TileDB-SOMA Pybind11 code. I want to check again tomorrow morning. For now, can you please run pre-commit run -a -v to correct the formatting?

@robertbindar
Copy link
Contributor Author

robertbindar commented Jan 12, 2024

@nguyenv I saw a fix related in a SOMA pybind11 PR, I'll update formatting in a bit, thanks.

@johnkerl johnkerl changed the title Fix ambiguos capsule calls with pybind11 Fix ambiguous capsule calls with pybind11 Jan 12, 2024
@ihnorton ihnorton merged commit ca0ccd7 into dev Feb 14, 2024
34 checks passed
@ihnorton ihnorton deleted the rbin/capsule_errors branch February 14, 2024 18:18
@ihnorton
Copy link
Member

Thanks @robertbindar

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.

3 participants