-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
UBSAN issue with Hamming due misalignment #456
Comments
It should be trivial to fix, and every reasonable C++ library should be tested with ASan+MSan+TSan+UBSan+Fuzzing. |
rschu1ze
added a commit
to rschu1ze/ClickHouse
that referenced
this issue
May 14, 2024
- this method is little to not found in other vector search offerings - it work kind of well for low dimensions but it suffers badly from a curse of dimensionality which makes inapt for a high number of dimensions - now that Annoy with spotify/annoy#456 is gone, we can drop 'no-ubsan', 'no-cpu-aarch64', and 'no-asan' from tests
rschu1ze
added a commit
to rschu1ze/ClickHouse
that referenced
this issue
Jun 10, 2024
Annoy indexes not popular these days, at least when it comes to vector databases. Such indexes work okay-ish low dimensions but they suffers badly from a curse of dimensionality which makes them inapt for a high number of dimensions. Now that Annoy is gone, issue (*) also disappears and we can drop 'no-ubsan', 'no-cpu-aarch64', and 'no-asan' from tests. (*) spotify/annoy#456
rschu1ze
added a commit
to rschu1ze/ClickHouse
that referenced
this issue
Aug 12, 2024
Annoy indexes fell out of favor in the community, at least when it comes to vector databases. Such indexes work okay-ish low dimensions but they suffers badly from a curse of dimensionality which makes them inapt for a high number of dimensions. Now that Annoy is gone, issue (*) also disappears and we can drop 'no-ubsan', 'no-cpu-aarch64', and 'no-asan' from tests. (*) spotify/annoy#456
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actually this PR won't fix that issue, and I'm not sure how to even fix it. Some thoughts:
v[i]
to not use an array dereferenceNone of these are entirely trivial
Originally posted by @erikbern in #455 (comment)
The text was updated successfully, but these errors were encountered: