Bug: Segfault on macOS when adding items to an index?

[davnn]

Describe the bug

Tests fail on macOS during add using exact search with f64, otherwise default parameters.

Steps to reproduce

Unfortunately, no access to a macOS device, the CI tests fail with

Fatal Python error: Segmentation fault

Thread 0x00000001f2608f40 (most recent call first):
  File "/Users/runner/Library/Caches/pypoetry/virtualenvs/nearness-5Zhs2NUM-py3.10/lib/python3.10/site-packages/usearch/index.py", line 275 in _add_to_compiled
  File "/Users/runner/Library/Caches/pypoetry/virtualenvs/nearness-5Zhs2NUM-py3.10/lib/python3.10/site-packages/usearch/index.py", line 666 in add

Expected behavior

Tests should pass as on other platforms.

USearch version

v2.16.6

Operating System

macOS

Hardware architecture

x86

Which interface are you using?

Python bindings

Contact Details

No response

Are you open to being tagged as a contributor?

• I am open to being mentioned in the project .git history as a contributor

Is there an existing issue for this?

• I have searched the existing issues

Code of Conduct

• I agree to follow this project's Code of Conduct

[ashvardanian]

@davnn, to clarify, are other numeric types working fine? Can you please print the hardware capabilities of your machine, logging your index like this:

$ python -c 'from usearch.index import Index; print(Index(ndim=768, metric="cos", dtype="f16").hardware_acceleration)'
> sapphire
$ python -c 'from usearch.index import Index; print(Index(ndim=166, metric="tanimoto").hardware_acceleration)'
> ice

[davnn]

Difficult, because I have no access to a macOS-device other than the CI-pipeline. Would be great if someone could reproduce using a macOS device, otherwise I would create a repository running some checks on a macOS runner, but that would take some time..

[ashvardanian]

We have a CI that checks MacOS Python builds. Is your MacOS version matching our prerelease.yml pipeline?