-
Notifications
You must be signed in to change notification settings - Fork 247
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
"cannot import name 'BUFSIZE' from 'numpy'" - traceback from "Sanity Check" #660
Comments
Yes, deepspeed tracks this as well: microsoft/DeepSpeed#5671 As a workaround, they suggest fixing the numpy version to <2.0.0. There are several ways to do this like adding another pip command at the end of the Dockerfile to install it |
Yes, pls downgrade numpy to 1.26.4 as a workaround. |
@YuningQiu the only problem I had building the docker image was related to need for proxy specification.
|
Thanks @BrianSwift-Intel ! For this issue, do you have other questions, or can we close this issue? |
Built v2.3.100 docker image per instructions at https://intel.github.io/intel-extension-for-pytorch/#installation?platform=cpu&version=v2.3.100%2bcpu&os=linux%2fwsl2&package=docker for "* Install from prebuilt wheel files" and ran "sanity check"
Also did 3.3 Docker-based environment setup with compilation from source and executed some llama2 performance test. All worked without producing "cannot import name 'BUFSIZE' from 'numpy'" - traceback |
Describe the bug
After building docker image following [RECOMMENDED] Docker-based environment setup with pre-built wheels executing Sanity Check results in traceback:
A docker image I built with the same process Friday (6/14/2024) works ok.
Maybe this is related to numpy version change to 2.0.0 that was just released (6/16/2024).
Versions
In the docker image that works, numpy version is 1.26.4
The text was updated successfully, but these errors were encountered: