Repository navigation
fix: vllm cache in subfolder to prevent python import conflict - #18
Merged
Merged
Conversation
Panaetius
force-pushed
the
fix/gemm-import
branch
from
October 21, 2026 10:29
7fc7df3 to
faf479c
Compare
cmdoret
approved these changes
Oct 21, 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
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.
there's a stupid bug because vllm cache root is e.g. /myhome and $HOME is also /myhome. on first start it will create a $CACHE/deep_gemm folder, but the python code somewhere has a import deep_gemm and $HOME is on python path, so instead of importing the library, it tries to import the cached checkpoint which obviously fails.
This puts the cache path a $HOME/.cache/vllm so there's no conflict.