fix(closes OPEN-8569): handle missing active trace and improve error logging in LiteLLM integration #569
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
viniciusdsmello
changed the title
shah-siddd
approved these changes
Dec 29, 2025
…logging in LiteLLM integration
viniciusdsmello
force-pushed
the
vini/open-8569-bug-trace-context-is-lost-when-using-asgi-workers
branch
from
256cb4c to
2710dc9
Compare
viniciusdsmello
deleted the
vini/open-8569-bug-trace-context-is-lost-when-using-asgi-workers
branch
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request
Summary
Fix context loss issue in LiteLLM streaming traces when generators are partially consumed or run in ASGI worker threads.
Changes
contextvars.Contextinlitellm_tracer.pyusingcopy_context()andcaptured_context.run()for trace finalizationloggerduring Python interpreter shutdown in streamingfinallyblockContext
When using LiteLLM streaming with FastAPI/Starlette, traces showed "Processing..." and
nulloutput. Root cause:contextvarsdon't propagate when generators are consumed in different threads (viaanyio.to_thread). The fix captures context at generator creation and restores it when finalizing the trace.Testing