Non-CUDA docker install failure due to build problems involving uv

Open
#375 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, pandas, python

Research direction

Start by reproducing the non-CUDA container failure with the reported docker exec command and inspect the pyproject.toml files reached by find. Trace the uv sync failures under /app/whisperx-env/WhisperX and /app/whisperx-env/pyannote, including the pandas build errors. Done means the non-CUDA model environments initialize and the reported Scriberr URL is reachable.

Written by the indexing model from the issue text.

Description

When running the non-CUDA version, the following output results (twice):

time=19:56:59 level=ERROR msg="Failed to initialize transcription model" model_id=canary error="failed to setup Canary environment: uv sync failed: exit status 2: warning: Failed to parse `pyproject.toml` during settings discovery:\n  TOML parse error at line 41, column 5\n     |\n  41 | cpu\"\n     |     ^\n  key with no value, expected `=`\n\nerror: Failed to parse: `pyproject.toml`\n  Caused by: TOML parse error at line 41, column 5\n   |\n41 | cpu\"\n   |     ^\nkey with no value, expected `=`"
time=19:56:59 level=ERROR msg="Failed to initialize diarization model" model_id=sortformer error="failed to setup Sortformer environment: uv sync failed: exit status 2: warning: Failed to parse `pyproject.toml` during settings discovery:\n  TOML parse error at line 41, column 5\n     |\n  41 | cpu\"\n     |     ^\n  key with no value, expected `=`\n\nerror: Failed to parse: `pyproject.toml`\n  Caused by: TOML parse error at line 41, column 5\n   |\n41 | cpu\"\n   |     ^\nkey with no value, expected `=`"
time=19:56:59 level=ERROR msg="Failed to initialize transcription model" model_id=parakeet error="failed to setup Parakeet environment: uv sync failed: exit status 2: warning: Failed to parse `pyproject.toml` during settings discovery:\n  TOML parse error at line 41, column 5\n     |\n  41 | cpu\"\n     |     ^\n  key with no value, expected `=`\n\nerror: Failed to parse: `pyproject.toml`\n  Caused by: TOML parse error at line 41, column 5\n   |\n41 | cpu\"\n   |     ^\nkey with no value, expected `=`"

Running the following uv command identifies the problem (for some reason, however, I simply cannot locate the offending pyproject.toml file on the file system):

$ docker exec -it 44ec58da6719 /bin/bash -c 'find . -name "pyproject.toml" -execdir uv sync \;'
warning: Failed to parse `pyproject.toml` during settings discovery:
  TOML parse error at line 41, column 5
     |
  41 | cpu"
     |     ^
  key with no value, expected `=`

error: Failed to parse: `pyproject.toml`
  Caused by: TOML parse error at line 41, column 5
   |
41 | cpu"
   |     ^
key with no value, expected `=`
Resolved 152 packages in 0.59ms
Audited 127 packages in 1ms
Using CPython 3.11.14 interpreter at: /usr/local/bin/python3
Creating virtual environment at: .venv
  × Failed to build `pandas @ file:///app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `mesonpy.build_editable` failed (exit status: 1)

      [stdout]
      + meson setup /app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas /app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas/build/cp311 -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --vsenv
      --native-file=/app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas/build/cp311/meson-python-native-file.ini

      ERROR: Neither source directory '/app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas' nor build directory '/app/whisperx-env/WhisperX/.venv/lib/python3.10/site-packages/pandas/build/cp311' contain a build file meson.build.

      hint: This usually indicates a problem with the package or the build environment.
Resolved 130 packages in 0.52ms
Audited 114 packages in 0.93ms
Using CPython 3.11.14 interpreter at: /usr/local/bin/python3
Creating virtual environment at: .venv
  × Failed to build `pandas @ file:///app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `mesonpy.build_editable` failed (exit status: 1)

      [stdout]
      + meson setup /app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas /app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas/build/cp311 -Dbuildtype=release -Db_ndebug=if-release -Db_vscrt=md --vsenv
      --native-file=/app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas/build/cp311/meson-python-native-file.ini

      ERROR: Neither source directory '/app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas' nor build directory '/app/whisperx-env/pyannote/.venv/lib/python3.11/site-packages/pandas/build/cp311' contain a build file meson.build.

      hint: This usually indicates a problem with the package or the build environment.

Incidentally, I do get the message "Scriberr is ready" url=http://0.0.0.0:8080, but I cannot connect to it.

Dominant language
Go
Stars
3.1k
Forks
264
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from rishikanthc/Scriberr

All issues in rishikanthc/Scriberr

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.