feat: improves lanchain callback context management #551
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
gustavocidornelas
approved these changes
Nov 24, 2025
gustavocidornelas
deleted the
vini/improves-lanchain-callback-context-management
branch
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
Refactored
AsyncOpenlayerHandlerto use a boolean flag for external trace detection instead of storing trace object reference. Improves code clarity and simplifies the integration pattern for external systems (e.g., LangFlow).Changes
NonechecksContext
Supports LangFlow integration where the handler needs to detect if it's operating within an external trace context. When an external context exists, the handler creates standalone traces in
_traces_by_rootfor integration by the external system instead of uploading independently.The refactor simplifies this by storing only a boolean flag captured at initialization, since we only need to know "was there an external trace?" not the trace object itself.
Testing