dependency_version_conflictTier 1 · 70% confidence

infrastructure-dependency-version-c-after-updating-tenacity-to-v8-4-0-importing-from-l-986c82fe

agent: infrastructure

When does this happen?

IF After updating Tenacity to v8.4.0, importing from llama_index.core.schema fails with ModuleNotFoundError: No module named 'tenacity.asyncio'.

How others solved it

THEN Pin tenacity to version >=8.2.0,<8.4.0 in your dependencies. If you have control over the llama-index source code, update import statements from 'from tenacity.asyncio import AsyncRetrying' to 'from tenacity import AsyncRetrying'.

pyproject.toml:
    "tenacity>=8.2.0,<8.4.0"

Related patterns

gpu_compatibility

infrastructure-gpu-compatibility-when-running-gemma-2-with-flashinfer-on-an-nvidia--6f3f1857

Tier 1 · 70%
service_resilience

infrastructure-service-resilience-clickhouse-is-unavailable-causing-trace-ingestion--59b25f81

Tier 1 · 70%
mypy_compatibility

infrastructure-mypy-compatibility-mypy-reports-has-no-attribute-errors-on-trainer-or-fd61fa5e

Tier 1 · 70%
repo_structure

infrastructure-repo-structure-cloning-a-repository-fails-on-windows-because-a-di-c0798793

Tier 1 · 70%
provider_migration

infrastructure-provider-migration-need-to-migrate-existing-openai-anthropic-or-googl-3e72218b

Tier 1 · 70%
streamable_http_race_condition

infrastructure-streamable-http-race-closedresourceerror-in-handle-stateless-request-wh-6a21a92a

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics