-
Notifications
You must be signed in to change notification settings - Fork 668
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
Tries to access root lock file #620
Comments
hit the same issue. w/o is to catch the errno==13 and skip |
Same here. It happens on versions 0.40.1 and 0.40.2 (I have yet to test older versions). |
My work around is to run as root (obviously not great)
thanks,
Lak
…On Fri, Jul 21, 2023, 8:35 AM Hannes Hapke ***@***.***> wrote:
Same here. It happens on versions 0.40.1 and 0.40.2 (I have yet to test
older versions).
It occurs in a Google Cloud compute instance (plain instance, not Vertex).
—
Reply to this email directly, view it on GitHub
<#620 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANJPZ5KS7DBZGPCQXVLOOLXRKOVPANCNFSM6AAAAAA2SAXQKY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
The permission error occurred when I tried to load a script. I narrowed down the imports to
and then the error was more specific
The error got resolved after installing |
Thanks, Hannes! Looks like this was fixed 4 days ago:
8a20cd8
Curious why it isn't fixed when you install from source.
|
Thank you, @lakshmanok, for pointing out the change. I tried to install it from source (before learning about the missing |
Also seeing this issue on my side, let me know if there's anything I can do to help with a clearer report. Also: installing scipy did not work (already installed), I'll attempt using |
Actually @hanneshapke do you know the exact image name (that's findable when starting a new instance) for |
I was able to get around this by adding to the set happy to pr this if it's a right soln - this would likely only affect GCP setups. |
This is great! It fixed the issue. Please push to the main branch.. |
PR is up- #785 |
@xaptronic -- Any ideas on how to address this when working in a vertex workbench? I don't have access to |
@madhavthaker1 that's not necessarily where the bitsandbytes config will be. It depends on your system/virtual envs etc. Run pip show bitsandbytes to find that path. |
@madhavthaker1 on vertex workbench, it might be in a path like "/opt/conda/lib/python3.10/site-packages/bitsandbytes/cuda_setup/env_vars.py" |
See this comment: bitsandbytes-foundation#620 (comment) adding this variable to be ignored allows the bitsandbytes import and setup to proceed on a GCP VM in a jupyter notebook.
Thanks all for debugging and providing the fix! Closing this, as the fix is now merged. Will be made available with the next release. |
See this comment: bitsandbytes-foundation#620 (comment) adding this variable to be ignored allows the bitsandbytes import and setup to proceed on a GCP VM in a jupyter notebook.
See this comment: bitsandbytes-foundation/bitsandbytes#620 (comment) adding this variable to be ignored allows the bitsandbytes import and setup to proceed on a GCP VM in a jupyter notebook.
Result of python -m bitsandbytes:
The problem persists even after compiling from source. I'm running in a Jupyter notebook (Google Cloud Vertex AI)
The text was updated successfully, but these errors were encountered: