Skip to content

πŸ› Bug: requirements with version ranges are installed via shell without quoting (< / > interpreted as redirects)Β #880

@anxety-solo

Description

@anxety-solo

Description

After recent updates of the extension, dependency installation started to fail on a clean setup.

The problem is not reported clearly as a packaging / shell issue, but instead surfaces as confusing errors like cannot open 15, cannot open 3.0.0, etc.

This appears to be caused by installing requirements with version ranges without proper shell-escaping or argument splitting, e.g.:

pip install av>=14,<15

which is interpreted by /bin/sh as input redirection (<15) instead of a version specifier.


Environment

  • WebUI: classic
  • Python: 3.11.13 (standalone build)
  • Python runtime: VENV created from standalone Python build
  • OS: Linux (Google Colab)
  • pip: from venv

Error log

Python 3.11.13 (main, Oct  7 2025, 15:35:45) [Clang 20.1.4 ]
Version: classic

Installing sd-webui-infinite-image-browsing requirement: av>=14,<15
Couldn't install sd-webui-infinite-image-browsing requirement: av>=14,<15.
Command: "/root/venv/bin/python3" -m pip install av>=14,<15 --prefer-binary
Error code: 2
stderr: /bin/sh: 1: cannot open 15: No such file

Installing sd-webui-infinite-image-browsing requirement: requests>=2.0.0,<3.0.0
stderr: /bin/sh: 1: cannot open 3.0.0: No such file

Installing sd-webui-infinite-image-browsing requirement: numpy>=1.10.0,<3.0.0
stderr: /bin/sh: 1: cannot open 3.0.0: No such file

Installing sd-webui-infinite-image-browsing requirement: hnswlib>=0.0.0,<1.0.0
stderr: /bin/sh: 1: cannot open 1.0.0: No such file

Expected behavior: Requirements with version ranges (comma-separated) should be installed correctly

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions