Deployment failed: Error during processing dependencies! Please fix the error and push an update, or try restarting the app

Hi, I’m getting this weird error where it says that numpy is not defined when numpy is literally the first thing to be installed, can you please help me with that?

I’m using python 3.11.6 and streamlit >= 1.9.2

That’s my GitHub repo for that project: GitHub - Aml-Hassan-Abd-El-hamid/ai-lip-sync-app
The log for reference:

[01:00:39] 🖥 Provisioning machine...

[01:00:44] 🎛 Preparing system...

[01:00:51] ⛓ Spinning up manager process...

[01:00:56] 🎈 Inflating balloons...

[01:00:40] 🚀 Starting up repository: 'ai-lip-sync-app', branch: 'main', main module: 'app.py'

[01:00:40] 🐙 Cloning repository...

[01:00:45] 🐙 Cloning into '/mount/src/ai-lip-sync-app'...
Warning: Permanently added the ED25519 host key for IP address '192.30.255.113' to the list of known hosts.

[01:00:45] 🐙 Cloned repository!

[01:00:45] 🐙 Pulling code changes from Github...

[01:00:46] 📦 Processing dependencies...

──────────────────────────────────────── pip ───────────────────────────────────────────

Collecting numpy==1.26.3

  Downloading numpy-1.26.3-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (18.3 MB)

     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 18.3/18.3 MB 361.9 MB/s eta 0:00:00[2024-01-23 01:00:47.981201] 

Collecting scipy==1.12.0

  Downloading scipy-1.12.0-cp311-cp311-manylinux_2_17_x86_64.manylinux2014_x86_64.whl (38.4 MB)

     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 38.4/38.4 MB 268.4 MB/s eta 0:00:00[2024-01-23 01:00:48.375294] 

Collecting iou==0.1.0

  Downloading iou-0.1.0.tar.gz (10 kB)

  Preparing metadata (setup.py): started

  Preparing metadata (setup.py): finished with status 'done'

Collecting librosa==0.10.1

  Downloading librosa-0.10.1-py3-none-any.whl (253 kB)

     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 253.7/253.7 KB 130.6 MB/s eta 0:00:00

Collecting lws==1.2.8

  Downloading lws-1.2.8.tar.gz (140 kB)

     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 140.5/140.5 KB 192.5 MB/s eta 0:00:00

  Preparing metadata (setup.py): started

  Preparing metadata (setup.py): finished with status 'error'

  error: subprocess-exited-with-error

  

  × python setup.py egg_info did not run successfully.

  │ exit code: 1

  ╰─> [6 lines of output]

      Traceback (most recent call last):

        File "<string>", line 2, in <module>

        File "<pip-setuptools-caller>", line 34, in <module>

        File "/tmp/pip-install-fp32o7ad/lws_66ea7375d4d84a689349350797a66aa1/setup.py", line 2, in <module>

          import numpy as np

      ModuleNotFoundError: No module named 'numpy'

      [end of output]

  

  note: This error originates from a subprocess, and is likely not a problem with pip.

error: metadata-generation-failed

× Encountered error while generating package metadata.

╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.

hint: See above for details.

WARNING: You are using pip version 22.0.3; however, version 23.3.2 is available.

You should consider upgrading via the '/home/adminuser/venv/bin/python -m pip install --upgrade pip' command.

Checking if Streamlit is installed

────────────────────────────────────────────────────────────────────────────────────────

[01:00:49] ❗️ installer returned a non-zero exit code

[01:00:49] ❗️ Error during processing dependencies! Please fix the error and push an update, or try restarting the app.

[01:02:21] ❗️ Streamlit server consistently failed status checks

[01:02:21] ❗️ Please fix the errors, push an update to the git repo, or reboot the app.

Hi @Aml

I noticed in the requirements.txt file that there were some spaces between the package name and version number:

streamlit >= 1.9.2 

Could you strip out the empty spaces.

After which, could you try rebooting the app to allow the server to re-install again.

1 Like

pip is trying to generate package metadata before installing anything. Try deploying the app without listing lws as a dependency. When all the other packages have been installed, add lws to requirements.txt and reboot the app if necessary.

1 Like

Thank you very much.
That did really solve the problem.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.