Skip to content

[FIX] Monkey-patch litellm cohere embed timeout for Bedrock embeddings#1848

Open
pk-zipstack wants to merge 29 commits intomainfrom
fix/litellm-cohere-embed-timeout
Open

[FIX] Monkey-patch litellm cohere embed timeout for Bedrock embeddings#1848
pk-zipstack wants to merge 29 commits intomainfrom
fix/litellm-cohere-embed-timeout

Conversation

@pk-zipstack
Copy link
Contributor

@pk-zipstack pk-zipstack commented Mar 11, 2026

What

Monkey-patch litellm's cohere embed handler to correctly forward the timeout parameter to client.post() calls, fixing "Connection timed out after None seconds" errors when indexing large documents with AWS Bedrock embedding models.

Why

litellm (v1.81.7) has a bug in litellm/llms/cohere/embed/handler.py where both embedding() and async_embedding() receive a timeout parameter but never forward it to client.post(). This causes the timeout to default to None, which surfaces as:

Connection timed out after None seconds.

This affects all Bedrock Cohere embedding operations (e.g. cohere.embed-multilingual-v3) and is especially visible with large documents. The bug is present on litellm's latest main branch as well — no upstream fix exists.

How

  • Added a monkey-patch module (unstract/sdk1/patches/litellm_cohere_timeout.py) that replaces the affected functions with versions that correctly pass timeout=timeout to client.post()
  • Patches three targets: the cohere handler module, the async variant, and bedrock's direct import binding (cohere_embedding)
  • Includes a version guard that skips the patch entirely if litellm is upgraded past 1.81.7, with a DeprecationWarning to prompt verification
  • Each patched function has inline comments marking the single line changed (# ONLY CHANGE)
  • Patch is activated via side-effect import from unstract.sdk1.embedding

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

No. The patched functions are exact copies of litellm 1.81.7's originals with only timeout=timeout added to client.post() calls. litellm is pinned at 1.81.7 in sdk1, so the source won't change. If litellm is later upgraded, the version guard skips the patch entirely and emits a warning.

Database Migrations

  • None

Env Config

  • None

Relevant Docs

  • N/A

Related Issues or PRs

  • Fixes Bedrock embedding timeout issue reported on staging with large documents (e.g. Large_1040.pdf)

Dependencies Versions

  • litellm: 1.81.7 (pinned, bug present)
  • httpx: 0.28.1

Notes on Testing

  • 6 unit tests added covering:
    • Sync path: timeout value (600.0), None timeout, httpx.Timeout object all forwarded correctly
    • Async path: timeout value forwarded correctly
    • Monkey-patch wiring: cohere handler and bedrock handler both point to patched functions
  • All tests pass: uv run pytest tests/patches/test_litellm_cohere_timeout.py -v

Screenshots

N/A

Checklist

I have read and understood the Contribution Guidelines.

🤖 Generated with Claude Code

pk-zipstack and others added 3 commits March 10, 2026 14:44
litellm's cohere embed handler (1.80.0) receives a timeout parameter
but doesn't pass it to client.post(), causing "Connection timed out
after None seconds" on large Bedrock embedding requests.

This adds a monkey-patch that replaces the affected functions with
versions that correctly forward timeout. Includes version guard,
source comments, and unit tests.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ions

- Version guard now skips patch entirely when litellm > 1.80.0
  instead of just warning
- Test assertions now check exact timeout value received by
  client.post(), not just that it was called
- Inline comments at client.post() calls marked with ONLY CHANGE

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 11, 2026

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Walkthrough

Adds a new patches package and a litellm Cohere timeout monkey-patch (sync + async) that forwards timeout arguments to underlying HTTP client calls; the patch is applied by a side-effect import in the SDK embedding module and unit tests verify timeout propagation and wiring.

Changes

Cohort / File(s) Summary
Patch package initializer
unstract/sdk1/src/unstract/sdk1/patches/__init__.py
New package initializer documenting that patches are applied via side-effect imports and noting activation from the SDK embedding module.
Cohere timeout monkey-patch
unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py
New monkey-patch adding _patched_async_embedding and _patched_embedding that forward timeout to underlying HTTP client post() calls, install into litellm handlers under a version guard, and emit a RuntimeWarning when not applied.
Activation via embedding module
unstract/sdk1/src/unstract/sdk1/embedding.py
Single-line side-effect import added to load and apply the patch when the embedding module is imported.
Tests for the patch
unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py
New tests covering sync and async embedding paths, asserting timeout propagation (numeric, None, httpx.Timeout) to HTTP client post() and verifying litellm handler replacement.
Project metadata
requirements.txt, pyproject.toml
Manifest files present in the diff set (no functional edits reported).

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant SDK as "SDK embedding\n(unstract.sdk1.embedding)"
    participant Patch as "Patch module\n(litellm_cohere_timeout)"
    participant Litellm as "litellm embed\nhandler (wrapped)"
    participant HTTP as "HTTP client\n(e.g., httpx)"

    User->>SDK: call embed(inputs, timeout=...)
    SDK->>Patch: import (side-effect) / use patched handler
    Patch->>Litellm: invoke wrapped handler
    Litellm->>HTTP: client.post(..., timeout=passed_timeout)
    HTTP-->>Litellm: response
    Litellm-->>Patch: embedding result
    Patch-->>SDK: return embeddings
    SDK-->>User: return embeddings
Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The pull request title accurately describes the main change: adding a monkey-patch for litellm's cohere embed timeout issue affecting Bedrock embeddings.
Description check ✅ Passed The pull request description comprehensively covers all required template sections with clear, detailed information about the changes, rationale, implementation, risk assessment, and testing.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/litellm-cohere-embed-timeout
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

pre-commit-ci bot and others added 3 commits March 11, 2026 10:45
- Remove useless self-assignment `model = model`
- Use int timeout values in tests to avoid float equality checks
- Use `is` identity checks instead of `==` for timeout assertions
- Replace async mock_post with AsyncMock to properly use async features

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py (1)

7-10: Exercise the production import hook in one test.

Because this file imports the patch module directly, the wiring checks only prove direct-import behavior. Add one integration test that imports unstract.sdk1.embedding and asserts the handler is patched, so Line 7 in unstract/sdk1/src/unstract/sdk1/embedding.py cannot regress silently.

Also applies to: 194-203

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py` around lines 7 -
10, Add an integration test that imports unstract.sdk1.embedding (instead of
importing the patch module directly) and asserts the production import hook
applied the patch: after importing unstract.sdk1.embedding, verify the module's
embedding handler uses the patched implementations by checking that its async
and sync embedding callables resolve to the symbols _patched_async_embedding and
_patched_embedding (or that their identities/reference equality match those
functions imported from unstract.sdk1.patches.litellm_cohere_timeout); update or
add this assertion into test_litellm_cohere_timeout.py alongside the existing
direct-import checks so the production import wiring (line referencing
unstract.sdk1.embedding) is exercised and cannot regress.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Around line 26-43: The patch currently imports private litellm.llms.* modules
before checking _SKIP_PATCH and uses a loose version check, so move all
private/internal imports (e.g., validate_environment, CohereEmbeddingConfig,
AsyncHTTPHandler, HTTPHandler, get_async_httpx_client, CohereEmbeddingRequest,
EmbeddingResponse and any litellm.llms.* import lines) to after the guard that
computes _SKIP_PATCH, change the version gate from a ">" check to an exact
equality check against the known compatible LiteLLM version, and when skipping
emit a visible warning via warnings.warn (not just DeprecationWarning swallowed
by default) so callers know the patch was skipped; ensure functions/classes
referenced in the patch (validate_environment, CohereEmbeddingConfig,
AsyncHTTPHandler, HTTPHandler, get_async_httpx_client, CohereEmbeddingRequest,
EmbeddingResponse) are only imported after the guard.

---

Nitpick comments:
In `@unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py`:
- Around line 7-10: Add an integration test that imports unstract.sdk1.embedding
(instead of importing the patch module directly) and asserts the production
import hook applied the patch: after importing unstract.sdk1.embedding, verify
the module's embedding handler uses the patched implementations by checking that
its async and sync embedding callables resolve to the symbols
_patched_async_embedding and _patched_embedding (or that their
identities/reference equality match those functions imported from
unstract.sdk1.patches.litellm_cohere_timeout); update or add this assertion into
test_litellm_cohere_timeout.py alongside the existing direct-import checks so
the production import wiring (line referencing unstract.sdk1.embedding) is
exercised and cannot regress.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f70cb6f9-69dd-431a-97bc-906d92c597ff

📥 Commits

Reviewing files that changed from the base of the PR and between c41e05e and dcd0663.

📒 Files selected for processing (5)
  • unstract/sdk1/src/unstract/sdk1/embedding.py
  • unstract/sdk1/src/unstract/sdk1/patches/__init__.py
  • unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py
  • unstract/sdk1/tests/patches/__init__.py
  • unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py (1)

26-64: ⚠️ Potential issue | 🟠 Major

Move the private LiteLLM imports behind the guard and gate on the exact tested version.

Lines 26-43 still import private litellm.llms.* modules before _SKIP_PATCH is evaluated, so a future LiteLLM reorg can fail at import time instead of cleanly skipping. Also, Line 56 only skips > 1.80.0; for a copied private implementation, != is safer. The skip warning on Lines 58-64 uses DeprecationWarning, which is usually hidden for imported library code, so operators may never notice that the patch was not applied. With the provided dependency context showing LiteLLM 1.81.7, this path would currently skip.

🔧 Suggested fix
 import importlib.metadata
 import json
 import logging
 import warnings
 from collections.abc import Callable

 import httpx
 import litellm
-import litellm.llms.bedrock.embed.embedding as _bedrock_embed
-import litellm.llms.cohere.embed.handler as _cohere_handler
 from litellm.litellm_core_utils.litellm_logging import (
     Logging as LiteLLMLoggingObj,
 )
-from litellm.llms.cohere.embed.handler import (
-    validate_environment,
-)
-from litellm.llms.cohere.embed.v1_transformation import (
-    CohereEmbeddingConfig,
-)
-from litellm.llms.custom_httpx.http_handler import (
-    AsyncHTTPHandler,
-    HTTPHandler,
-    get_async_httpx_client,
-)
-from litellm.types.llms.bedrock import CohereEmbeddingRequest
-from litellm.types.utils import EmbeddingResponse
 from packaging.version import Version

 logger = logging.getLogger(__name__)

 _DEFAULT_TIMEOUT = httpx.Timeout(None)

 _PATCHED_LITELLM_VERSION = "1.80.0"
 _litellm_version = importlib.metadata.version("litellm")
-_SKIP_PATCH = Version(_litellm_version) > Version(_PATCHED_LITELLM_VERSION)
+_SKIP_PATCH = Version(_litellm_version) != Version(_PATCHED_LITELLM_VERSION)
 if _SKIP_PATCH:
     warnings.warn(
         "litellm_cohere_timeout patch was SKIPPED — not applied. "
         f"Current litellm version: {_litellm_version}. "
         f"Patch was written for: {_PATCHED_LITELLM_VERSION}. "
         "Please verify the upstream fix and remove this module.",
-        DeprecationWarning,
+        RuntimeWarning,
         stacklevel=2,
     )
+else:
+    import litellm.llms.bedrock.embed.embedding as _bedrock_embed
+    import litellm.llms.cohere.embed.handler as _cohere_handler
+    from litellm.llms.cohere.embed.handler import validate_environment
+    from litellm.llms.cohere.embed.v1_transformation import CohereEmbeddingConfig
+    from litellm.llms.custom_httpx.http_handler import (
+        AsyncHTTPHandler,
+        HTTPHandler,
+        get_async_httpx_client,
+    )
+    from litellm.types.llms.bedrock import CohereEmbeddingRequest
+    from litellm.types.utils import EmbeddingResponse
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py` around
lines 26 - 64, The current file imports private litellm modules before computing
_SKIP_PATCH, which can cause import-time failures; move all imports of
litellm.llms.* and litellm.litellm_core_utils.* (symbols: _bedrock_embed,
_cohere_handler, LiteLLMLoggingObj, validate_environment, CohereEmbeddingConfig,
AsyncHTTPHandler, HTTPHandler, get_async_httpx_client, CohereEmbeddingRequest,
EmbeddingResponse) so they occur only after computing _litellm_version and
_SKIP_PATCH; change the version check to use equality against
_PATCHED_LITELLM_VERSION (i.e. skip only when Version(_litellm_version) ==
Version(_PATCHED_LITELLM_VERSION) or gate with != as requested) and replace the
DeprecationWarning with a visible warning class such as UserWarning or
RuntimeWarning so operators see the warning when the patch is skipped.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Around line 26-64: The current file imports private litellm modules before
computing _SKIP_PATCH, which can cause import-time failures; move all imports of
litellm.llms.* and litellm.litellm_core_utils.* (symbols: _bedrock_embed,
_cohere_handler, LiteLLMLoggingObj, validate_environment, CohereEmbeddingConfig,
AsyncHTTPHandler, HTTPHandler, get_async_httpx_client, CohereEmbeddingRequest,
EmbeddingResponse) so they occur only after computing _litellm_version and
_SKIP_PATCH; change the version check to use equality against
_PATCHED_LITELLM_VERSION (i.e. skip only when Version(_litellm_version) ==
Version(_PATCHED_LITELLM_VERSION) or gate with != as requested) and replace the
DeprecationWarning with a visible warning class such as UserWarning or
RuntimeWarning so operators see the warning when the patch is skipped.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 651cf418-be2b-4238-bfe1-13ad72694bba

📥 Commits

Reviewing files that changed from the base of the PR and between dcd0663 and b93ac45.

📒 Files selected for processing (2)
  • unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py
  • unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py
🚧 Files skipped from review as they are similar to previous changes (1)
  • unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py

pk-zipstack and others added 2 commits March 12, 2026 09:29
- Move all litellm.llms.* imports inside the `if not _SKIP_PATCH`
  block so they're only loaded when the patch will be applied
- Change version gate from `>` to exact equality (`!=`) — patch
  only applies on the exact known-affected version (1.80.0)
- Use RuntimeWarning instead of DeprecationWarning for skip message
  so it's visible by default (DeprecationWarning is filtered)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Around line 30-41: The version guard (_PATCHED_LITELLM_VERSION,
_litellm_version, _SKIP_PATCH) causes the patch to be skipped because sdk1 uses
LiteLLM 1.81.7; update the constant _PATCHED_LITELLM_VERSION to "1.81.7" (and
run tests/verify that the Cohere timeout fix is effective in that release) or,
alternatively, revert sdk1's litellm dependency to "1.80.0" so the existing
patch applies—ensure the chosen approach makes _SKIP_PATCH False so the patch
code executes.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0422bc8a-b039-47cf-aeeb-e54e2c5640e2

📥 Commits

Reviewing files that changed from the base of the PR and between b93ac45 and f6181a6.

📒 Files selected for processing (1)
  • unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py

Copy link
Contributor

@hari-kuriakose hari-kuriakose left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@pk-zipstack LGTM overall.

However request few critical changes though.

pk-zipstack and others added 2 commits March 12, 2026 21:31
Co-authored-by: Hari John Kuriakose <hari@zipstack.com>
Signed-off-by: Praveen Kumar <praveen@zipstack.com>
@greptile-apps
Copy link
Contributor

greptile-apps bot commented Mar 12, 2026

Greptile Summary

This PR monkey-patches litellm 1.81.7's Cohere embed handler to fix a bug where the timeout parameter was never forwarded to client.post(), causing "Connection timed out after None seconds" errors on Bedrock Cohere embedding operations with large documents.

Key changes:

  • Adds unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py: the patch module, which replaces litellm.llms.cohere.embed.handler.embedding, async_embedding, and litellm.llms.bedrock.embed.embedding.cohere_embedding with versions that pass timeout=timeout to client.post(). A version guard applies the patch only when litellm is exactly 1.81.7.
  • Activates the patch via a side-effect import in unstract/sdk1/src/unstract/sdk1/embedding.py.
  • Adds 6 unit tests covering the sync path and monkey-patch wiring. The async path test mentioned in the PR description is absent from the final test file, leaving _patched_async_embedding's core fix untested.
  • pytest-asyncio is added to the test dependency group but has no corresponding async test to run, and no asyncio_mode is configured in pyproject.toml.

Confidence Score: 3/5

  • The sync embedding fix is sound and well-structured, but the async embedding path — which is the Bedrock async flow — has no test coverage for the timeout fix itself.
  • The patch mechanism is correct: module-level imports are used, all three call-site bindings are patched, and the version guard matches the pinned litellm version. However, the async path (_patched_async_embedding) is the one most at risk for Bedrock large-document indexing (the scenario that triggered this bug), and there is no test asserting that timeout reaches client.post() in that code path. Additionally, pytest-asyncio is a dead dependency and the version-skip warning uses a logger rather than warnings.warn, so engineers upgrading litellm may miss the notice entirely.
  • unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py — missing async path coverage; unstract/sdk1/pyproject.toml — unused pytest-asyncio dependency and no asyncio_mode config.

Important Files Changed

Filename Overview
unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py Core monkey-patch module: correctly imports _cohere_handler and _bedrock_embed, applies the timeout fix to all three call-site bindings, and uses a strict equality version guard. Version constant matches the pinned litellm version in pyproject.toml (1.81.7). Logger-based warning (rather than warnings.warn) means the skip notice won't be seen in test output without a logging handler configured.
unstract/sdk1/src/unstract/sdk1/embedding.py Side-effect import of the patch module added at line 7; no other changes. Activation is clean and well-documented.
unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py 6 tests cover the sync path and monkey-patch wiring, but the async path (testing that _patched_async_embedding forwards timeout to client.post()) is entirely absent despite being listed as a test case in the PR description. pytest-asyncio was added to support an async test but that test is not present in the final file.
unstract/sdk1/pyproject.toml Adds pytest-asyncio>=0.24.0 to the test dependency group. The dependency was added to support an async test, but no async test function exists in the current test file. No asyncio_mode is configured under [tool.pytest.ini_options].

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A["unstract.sdk1.embedding imported"] --> B["Side-effect import:\nlitellm_cohere_timeout"]
    B --> C{litellm version\n== 1.81.7?}
    C -- No --> D["logger.warning: patch SKIPPED\n(silent in most environments)"]
    C -- Yes --> E["Import _cohere_handler\n& _bedrock_embed modules"]
    E --> F["Define _patched_embedding\n(adds timeout= to client.post)"]
    E --> G["Define _patched_async_embedding\n(adds timeout= to client.post)"]
    F --> H["_cohere_handler.embedding\n= _patched_embedding"]
    G --> I["_cohere_handler.async_embedding\n= _patched_async_embedding"]
    F --> J["_bedrock_embed.cohere_embedding\n= _patched_embedding"]
    H & I & J --> K["Patch applied — Bedrock\nCohere embed calls now\nforward timeout correctly"]
Loading

Comments Outside Diff (2)

  1. unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py, line 33-41 (link)

    Version-skip notice uses logger.warning — invisible without a configured handler

    The skip notice is emitted via logger.warning(...). In most production deployments and in test environments where no logging handler is attached to this logger, the message is silently discarded. The intent (alerting engineers that the patch is inactive after a litellm upgrade) is better served by warnings.warn, which always reaches stderr regardless of the logging configuration:

    Using DeprecationWarning aligns with the PR description's stated intent and is suppressed in production by Python's default filter, surfacing only in development and test runs.

  2. unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py, line 1-10 (link)

    Async path timeout forwarding is untested

    The PR description explicitly lists "Async path: timeout value forwarded correctly" as one of the six tested scenarios, and it is the core of the bug being fixed. However, no test for _patched_async_embedding actually calling client.post(..., timeout=timeout) exists in the final file. The three sync tests verify _patched_embedding, and the three wiring tests verify module-level attribute identity — _patched_async_embedding's own client.post() call (line 109 of the patch) is never exercised by a test.

    This means the async embedding path (used when aembedding=True, which is the Bedrock async flow) has zero test coverage for the fix itself. A test similar to test_timeout_passed_to_client_post is needed, creating an AsyncMock for client.post, awaiting _patched_async_embedding(...) with a known timeout, and asserting the timeout value was forwarded in the post() call kwargs.

Prompt To Fix All With AI
This is a comment left during a code review.
Path: unstract/sdk1/pyproject.toml
Line: 71-78

Comment:
**`pytest-asyncio` added but unused — and `asyncio_mode` is not configured**

`pytest-asyncio>=0.24.0` was added to the test group (to support the async path test), but the current `tests/patches/test_litellm_cohere_timeout.py` contains no `async def test_*` functions. The dependency has no effect and adds unnecessary installation overhead.

If an async test is (re-)added later, `pytest-asyncio>=0.21` also requires an explicit `asyncio_mode` setting in `[tool.pytest.ini_options]`, otherwise it emits `PytestUnraisableExceptionWarning` on every run:

```toml
[tool.pytest.ini_options]
asyncio_mode = "auto"   # or "strict"
```

Consider either removing `pytest-asyncio` until an async test exists, or keeping it and adding the `asyncio_mode` configuration alongside.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py
Line: 33-41

Comment:
**Version-skip notice uses `logger.warning` — invisible without a configured handler**

The skip notice is emitted via `logger.warning(...)`. In most production deployments and in test environments where no logging handler is attached to this logger, the message is silently discarded. The intent (alerting engineers that the patch is inactive after a litellm upgrade) is better served by `warnings.warn`, which always reaches stderr regardless of the logging configuration:

```suggestion
    import warnings
    warnings.warn(
        f"litellm_cohere_timeout patch was SKIPPED — not applied. "
        f"Current litellm version: {_litellm_version}. "
        f"Patch was written for: {_PATCHED_LITELLM_VERSION}. "
        f"Please verify the upstream fix and remove this module.",
        DeprecationWarning,
        stacklevel=2,
    )
```

Using `DeprecationWarning` aligns with the PR description's stated intent and is suppressed in production by Python's default filter, surfacing only in development and test runs.

How can I resolve this? If you propose a fix, please make it concise.

---

This is a comment left during a code review.
Path: unstract/sdk1/tests/patches/test_litellm_cohere_timeout.py
Line: 1-10

Comment:
**Async path timeout forwarding is untested**

The PR description explicitly lists "Async path: timeout value forwarded correctly" as one of the six tested scenarios, and it is the core of the bug being fixed. However, no test for `_patched_async_embedding` actually calling `client.post(..., timeout=timeout)` exists in the final file. The three sync tests verify `_patched_embedding`, and the three wiring tests verify module-level attribute identity — `_patched_async_embedding`'s own `client.post()` call (line 109 of the patch) is never exercised by a test.

This means the async embedding path (used when `aembedding=True`, which is the Bedrock async flow) has zero test coverage for the fix itself. A test similar to `test_timeout_passed_to_client_post` is needed, creating an `AsyncMock` for `client.post`, awaiting `_patched_async_embedding(...)` with a known `timeout`, and asserting the timeout value was forwarded in the `post()` call kwargs.

How can I resolve this? If you propose a fix, please make it concise.

Last reviewed commit: "[FIX] Regenerate sdk..."

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🧹 Nitpick comments (1)
unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py (1)

15-15: Consider adding a TODO marker for discoverability.

Adding TODO: makes this line searchable via grep/IDE tooling, helping ensure timely removal once upstream fixes the bug.

-Remove this patch when litellm ships a fix upstream.
+TODO: Remove this patch when litellm ships a fix upstream.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py` at line
15, Update the top-of-file note in litellm_cohere_timeout.py so it includes a
searchable TODO marker; specifically replace or edit the comment "Remove this
patch when litellm ships a fix upstream." to start with "TODO:" (e.g., "TODO:
Remove this patch when litellm ships a fix upstream.") so it is discoverable via
grep/IDE and clearly signals removal once the upstream bug in litellm is fixed.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Around line 42-65: The code references module aliases `_cohere_handler` and
`_bedrock_embed` later but only imports individual symbols (e.g.,
validate_environment, CohereEmbeddingConfig, AsyncHTTPHandler,
get_async_httpx_client, LiteLLMLoggingObj, CohereEmbeddingRequest,
EmbeddingResponse); add explicit module imports for the cohere and bedrock embed
modules (import the modules as `_cohere_handler` and `_bedrock_embed`) inside
the same else block so the later references to `_cohere_handler` and
`_bedrock_embed` resolve at runtime.
- Around line 30-32: The version guard currently pins the patch to
_PATCHED_LITELLM_VERSION = "1.80.0" causing _SKIP_PATCH to be true at runtime
for the dependency _litellm_version (which is 1.81.7), so the timeout patch is
skipped; either update _PATCHED_LITELLM_VERSION to "1.81.7" if the timeout bug
still exists in that release, or remove this patch block entirely if the
upstream bug is fixed—modify the constant _PATCHED_LITELLM_VERSION accordingly
and verify the behavior of _SKIP_PATCH (which compares Version(_litellm_version)
!= Version(_PATCHED_LITELLM_VERSION)) so the patch will run only when intended.

---

Nitpick comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Line 15: Update the top-of-file note in litellm_cohere_timeout.py so it
includes a searchable TODO marker; specifically replace or edit the comment
"Remove this patch when litellm ships a fix upstream." to start with "TODO:"
(e.g., "TODO: Remove this patch when litellm ships a fix upstream.") so it is
discoverable via grep/IDE and clearly signals removal once the upstream bug in
litellm is fixed.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 42ebcad6-b1fa-4a6e-91c5-b75e12a511b5

📥 Commits

Reviewing files that changed from the base of the PR and between f6181a6 and 644da84.

📒 Files selected for processing (1)
  • unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

♻️ Duplicate comments (1)
unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py (1)

48-65: ⚠️ Potential issue | 🔴 Critical

Import the modules you rebind later.

This block imports symbols from the Cohere and Bedrock modules, but lines 213-215 assign through _cohere_handler and _bedrock_embed, which are never defined. On LiteLLM 1.81.7, importing this patch will raise NameError before the monkey-patch is applied, breaking the side-effect activation path from unstract.sdk1.embedding.

🐛 Proposed fix
     import httpx
     import litellm
+    import litellm.llms.bedrock.embed.embedding as _bedrock_embed
+    import litellm.llms.cohere.embed.handler as _cohere_handler
     from litellm.litellm_core_utils.litellm_logging import (
         Logging as LiteLLMLoggingObj,
     )
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py` around
lines 48 - 65, The patch imports Cohere/Bedrock symbols but later rebinds
globals like _cohere_handler and _bedrock_embed without first defining or
importing them, causing a NameError on import; to fix, import or define the
original symbols before rebinding (e.g., import the existing cohere handler and
bedrock embed functions used in lines that assign to _cohere_handler and
_bedrock_embed), then perform the monkey-patch assignments; locate the rebinding
logic targeting _cohere_handler and _bedrock_embed and ensure the original
symbols are referenced (via imports or safe getattr fallbacks) so the module can
be imported without raising NameError.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Duplicate comments:
In `@unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py`:
- Around line 48-65: The patch imports Cohere/Bedrock symbols but later rebinds
globals like _cohere_handler and _bedrock_embed without first defining or
importing them, causing a NameError on import; to fix, import or define the
original symbols before rebinding (e.g., import the existing cohere handler and
bedrock embed functions used in lines that assign to _cohere_handler and
_bedrock_embed), then perform the monkey-patch assignments; locate the rebinding
logic targeting _cohere_handler and _bedrock_embed and ensure the original
symbols are referenced (via imports or safe getattr fallbacks) so the module can
be imported without raising NameError.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e8692340-9a40-4b25-ac09-56dbde0e3fb8

📥 Commits

Reviewing files that changed from the base of the PR and between 644da84 and 419d5e9.

📒 Files selected for processing (1)
  • unstract/sdk1/src/unstract/sdk1/patches/litellm_cohere_timeout.py

pk-zipstack and others added 2 commits March 12, 2026 23:12
- Restore `_bedrock_embed` and `_cohere_handler` imports that were
  silently removed by ruff auto-fix (marked with noqa: F811)
- Add test verifying patch activation through the production import
  path (unstract.sdk1.embedding) per reviewer feedback
- Tests are tox-compatible — already covered by [testenv:sdk1] in
  tox.ini

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pk-zipstack and others added 5 commits March 13, 2026 09:53
Switch from RuntimeWarning to DeprecationWarning so the skip
message only surfaces in dev/test environments (Python suppresses
DeprecationWarning by default in production).

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…heck

The previous test used importlib.import_module which is a no-op for
already-cached modules. Replace with a sys.modules assertion that
verifies the patch module is loaded as a consequence of importing
unstract.sdk1.embedding.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Signed-off-by: Praveen Kumar <praveen@zipstack.com>
pk-zipstack and others added 2 commits March 13, 2026 15:15
Patch validate_environment alongside CohereEmbeddingConfig to
isolate tests from real litellm code. Prevents test breakage if
litellm changes validate_environment behavior in future versions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pk-zipstack and others added 2 commits March 13, 2026 15:27
Replace asyncio.run() wrapper with @pytest.mark.asyncio to avoid
RuntimeError when pytest-asyncio is present with a running event
loop. Add pytest-asyncio>=0.24.0 to test dependencies.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
pk-zipstack and others added 5 commits March 18, 2026 12:39
DeprecationWarning is suppressed by default in production, so operators
would not notice if the cohere timeout patch silently stops applying
after a litellm upgrade. Switch to logger.warning for visibility.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Async embedding paths are not used in our codebase. Removing the async
tests avoids the pytest-asyncio dependency and lock file churn across
6 services.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Reverting lock files to their original branch state. Removing
pytest-asyncio from pyproject.toml caused lock file mismatch
that broke Docker builds using --locked.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
The lock file was missing unstract-core and had stale package
versions, causing --locked builds to fail.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@github-actions
Copy link
Contributor

Test Results

Summary
  • Runner Tests: 11 passed, 0 failed (11 total)
  • SDK1 Tests: 69 passed, 0 failed (69 total)

Runner Tests - Full Report
filepath function $$\textcolor{#23d18b}{\tt{passed}}$$ SUBTOTAL
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_logs}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_cleanup}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_cleanup\_skip}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_client\_init}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_get\_image\_exists}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_get\_image}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_get\_container\_run\_config}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_get\_container\_run\_config\_without\_mount}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_run\_container}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_get\_image\_for\_sidecar}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{runner/src/unstract/runner/clients/test\_docker.py}}$$ $$\textcolor{#23d18b}{\tt{test\_sidecar\_container}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{TOTAL}}$$ $$\textcolor{#23d18b}{\tt{11}}$$ $$\textcolor{#23d18b}{\tt{11}}$$
SDK1 Tests - Full Report
filepath function $$\textcolor{#23d18b}{\tt{passed}}$$ SUBTOTAL
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestPatchedEmbeddingSyncTimeoutForwarding.test\_timeout\_passed\_to\_client\_post}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestPatchedEmbeddingSyncTimeoutForwarding.test\_none\_timeout\_passed\_to\_client\_post}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestPatchedEmbeddingSyncTimeoutForwarding.test\_httpx\_timeout\_object\_forwarded}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestMonkeyPatchApplied.test\_cohere\_handler\_patched}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestMonkeyPatchApplied.test\_bedrock\_handler\_patched}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/patches/test\_litellm\_cohere\_timeout.py}}$$ $$\textcolor{#23d18b}{\tt{TestMonkeyPatchApplied.test\_patch\_module\_loaded\_via\_embedding\_import}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_success\_on\_first\_attempt}}$$ $$\textcolor{#23d18b}{\tt{2}}$$ $$\textcolor{#23d18b}{\tt{2}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_retry\_on\_connection\_error}}$$ $$\textcolor{#23d18b}{\tt{2}}$$ $$\textcolor{#23d18b}{\tt{2}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_non\_retryable\_http\_error}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_retryable\_http\_errors}}$$ $$\textcolor{#23d18b}{\tt{3}}$$ $$\textcolor{#23d18b}{\tt{3}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_post\_method\_retry}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_platform.py}}$$ $$\textcolor{#23d18b}{\tt{TestPlatformHelperRetry.test\_retry\_logging}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_prompt.py}}$$ $$\textcolor{#23d18b}{\tt{TestPromptToolRetry.test\_success\_on\_first\_attempt}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_prompt.py}}$$ $$\textcolor{#23d18b}{\tt{TestPromptToolRetry.test\_retry\_on\_errors}}$$ $$\textcolor{#23d18b}{\tt{2}}$$ $$\textcolor{#23d18b}{\tt{2}}$$
$$\textcolor{#23d18b}{\tt{tests/test\_prompt.py}}$$ $$\textcolor{#23d18b}{\tt{TestPromptToolRetry.test\_wrapper\_methods\_retry}}$$ $$\textcolor{#23d18b}{\tt{4}}$$ $$\textcolor{#23d18b}{\tt{4}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_connection\_error\_is\_retryable}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_timeout\_is\_retryable}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_http\_error\_retryable\_status\_codes}}$$ $$\textcolor{#23d18b}{\tt{3}}$$ $$\textcolor{#23d18b}{\tt{3}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_http\_error\_non\_retryable\_status\_codes}}$$ $$\textcolor{#23d18b}{\tt{5}}$$ $$\textcolor{#23d18b}{\tt{5}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_http\_error\_without\_response}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_os\_error\_retryable\_errno}}$$ $$\textcolor{#23d18b}{\tt{5}}$$ $$\textcolor{#23d18b}{\tt{5}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_os\_error\_non\_retryable\_errno}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestIsRetryableError.test\_other\_exception\_not\_retryable}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCalculateDelay.test\_exponential\_backoff\_without\_jitter}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCalculateDelay.test\_exponential\_backoff\_with\_jitter}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCalculateDelay.test\_max\_delay\_cap}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCalculateDelay.test\_max\_delay\_cap\_with\_jitter}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_successful\_call\_first\_attempt}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_retry\_after\_transient\_failure}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_max\_retries\_exceeded}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_retry\_with\_custom\_predicate}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_no\_retry\_with\_predicate\_false}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryWithExponentialBackoff.test\_exception\_not\_in\_tuple\_not\_retried}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_default\_configuration}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_environment\_variable\_configuration}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_invalid\_max\_retries}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_invalid\_base\_delay}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_invalid\_multiplier}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_jitter\_values}}$$ $$\textcolor{#23d18b}{\tt{2}}$$ $$\textcolor{#23d18b}{\tt{2}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_custom\_exceptions\_only}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_custom\_predicate\_only}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_both\_exceptions\_and\_predicate}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestCreateRetryDecorator.test\_exceptions\_match\_but\_predicate\_false}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestPreconfiguredDecorators.test\_retry\_platform\_service\_call\_exists}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestPreconfiguredDecorators.test\_retry\_prompt\_service\_call\_exists}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestPreconfiguredDecorators.test\_platform\_service\_decorator\_retries\_on\_connection\_error}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestPreconfiguredDecorators.test\_prompt\_service\_decorator\_retries\_on\_timeout}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryLogging.test\_warning\_logged\_on\_retry}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryLogging.test\_info\_logged\_on\_success\_after\_retry}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{tests/utils/test\_retry\_utils.py}}$$ $$\textcolor{#23d18b}{\tt{TestRetryLogging.test\_exception\_logged\_on\_giving\_up}}$$ $$\textcolor{#23d18b}{\tt{1}}$$ $$\textcolor{#23d18b}{\tt{1}}$$
$$\textcolor{#23d18b}{\tt{TOTAL}}$$ $$\textcolor{#23d18b}{\tt{69}}$$ $$\textcolor{#23d18b}{\tt{69}}$$

@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants