Not sure if it's easily reproducible (it isn't even for me consistently), but during docker build, downloading the en_core_web_sm package fails with a 403 Server error, on occasion. With the --no-cache option during docker 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
python -m spacy download en_core_web_sm
Error message
81.32 ✘ Server error (403)
81.32 Couldn't fetch compatibility table. Please find a package for your spaCy
81.32 installation (v3.7.5), and download it manually. For more details, see the
81.32 documentation: https://spacy.io/usage/models
Your Environment
Operating System: Ubuntu 24.04 LTS
Python Version Used: 3.11
spaCy Version Used: 3.7.5
Environment Information: Conda environment within Docker, spaCy is downloaded with pip install -r requirements.txt
Lixiyao-meow
commented
1 day ago
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_smpackage fails with a 403 Server error, on occasion. With the--no-cacheoption 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