-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
403 Server Error: Downloading en_core_web_sm
fails due to "Compatibility table not found for Spacy v3.7.5"
#13690
Comments
en_core_web_sm
fails due to "Compatibility table not found for Spacy v3.7.5"en_core_web_sm
fails due to "Compatibility table not found for Spacy v3.7.5
Same issue here |
en_core_web_sm
fails due to "Compatibility table not found for Spacy v3.7.5en_core_web_sm
fails due to "Compatibility table not found for Spacy v3.7.5"
Same issue here |
Ditto, but with |
I am having the same issue but with SpaCy |
FixFigured out a fix. Use the following requirements in
Use line 2 above instead of downloading it via Root CauseThe direct download link throws a 404 for all SpaCy versions from 3.7.2 to 3.7.5: e.g. https://github.com/explosion/spacy-models/releases/download/en_core_web_sm-3.7.2/en_core_web_sm-3.7.2-py3-none-any.whl I tried downgrading to 3.7.1, and installing directly with
Following this odd recommendation (using |
Smae issue here. The simple quickstart from official spacy docs doesn't seem to work: |
This is affecting me as well. Is this being worked on? |
@cplonski20 figured out a workaround for it, see my comment above. |
Update 2: this was solved for me using an x86 machine, didn't find a way for it to work on linux-aarch64 Update: this is no longer working, installation fails at the Logs
|
How to reproduce the behaviour
Not sure if it's easily reproducible (it isn't even for me consistently), but during
docker build
, downloading theen_core_web_sm
package fails with a 403 Server error, on occasion. With the--no-cache
option duringdocker build
, it still fails occasionally, and retrying the build often leads to a success, but not always. This has only started happening since sometime early this week or late last week, there's been no code change at all for the build or for requirements, and I've never faced this issue prior to now. spaCy claims it can't find the compatibility table, but clearly it can when it doesn't fail.Failing command
Error message
Your Environment
pip install -r requirements.txt
The text was updated successfully, but these errors were encountered: