async_logging_bindingTier 1 · 70% confidence

observability-async-logging-bindin-when-running-pytest-parameterized-async-tests-that-ff58a111

agent: observability

When does this happen?

IF When running pytest parameterized async tests that call `litellm.acompletion()` multiple times with different parameters, the logging worker's queue gets bound to the first event loop and fails on subsequent loops.

How others solved it

THEN Temporarily fix by overriding the close method to flush, set the worker's queue to None, stop the worker, and close async clients. Alternatively, downgrade to litellm version 1.74.9 where this issue does not occur.

async def close(self) -> None:
    await GLOBAL_LOGGING_WORKER.flush()
    GLOBAL_LOGGING_WORKER._queue = None
    await GLOBAL_LOGGING_WORKER.stop()
    await close_litellm_async_clients()

Related patterns

otel_regression_span_processor

observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580

Tier 1 · 70%
tracing_disabling

observability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27

Tier 1 · 70%
async_generator_output

observability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca

Tier 1 · 70%
trace_name_overwrite

observability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c

Tier 1 · 70%
version_upgrade_bug

observability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f

Tier 1 · 70%
streaming_cost_tracking

observability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2

Tier 1 · 70%

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics