fix(vectordb): handle Windows 11 platform.machine() empty string and circular import - #3019
Merged
qin-ctx merged 2 commits intoJul 8, 2026
Merged
Conversation
…circular import - _is_x86_machine(): default to x86 on win32 when platform.machine() returns empty string (Windows 11 build 26200) - _module_exists(): catch ModuleNotFoundError during module init when __path__ is not yet assigned, fall back to filesystem .pyd check
qin-ctx
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
_is_x86_machine(): On Windows 11 (build 26200),platform.machine()returns an empty string, causing the engine to incorrectly treat the CPU as non-x86 and attempt to load a non-existentnativebackend. Fix: default to x86 onwin32when the machine string is empty._module_exists():importlib.util.find_spec()raisesModuleNotFoundErrorduring module initialization because__path__has not been assigned yet. This is a circular-import timing issue that makes the engine think zero backend variants are available. Fix: catch the exception and fall back to a filesystem.pydcheck.Test plan
_is_x86_machine()returnsTruewhenplatform.machine()is empty onwin32AMD64,aarch64) still works correctly_module_exists()does not crash whenfind_specraisesModuleNotFoundError.pydfiles