Skip to content

[harness][packaging] deerflow-harness imports requests without declaring it #2551

@hetaoBackend

Description

@hetaoBackend

Problem

The harness package imports requests in AIO sandbox/client code, but requests is not declared as a direct dependency in backend/packages/harness/pyproject.toml. The import can work in the monorepo because another package happens to provide it, but standalone installs are not guaranteed to have it.

Impact

A clean install of deerflow-harness can fail at runtime with ModuleNotFoundError: No module named 'requests' when those code paths are imported or used.

Suggested Fix

Add requests as a direct dependency of deerflow-harness, or migrate these paths to an already-declared HTTP client such as httpx.

Tests

  • Build/install deerflow-harness into a clean venv.
  • Import the AIO sandbox/client modules that currently import requests.
  • Verify imports succeed without relying on backend transitive dependencies.

References

  • backend/packages/harness/deerflow/community/aio_sandbox/backend.py:9
  • backend/packages/harness/deerflow/community/aio_sandbox/remote_backend.py:22
  • backend/packages/harness/deerflow/infoquest_client.py:12
  • backend/packages/harness/pyproject.toml:6

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions