fix(core): honor enabled=false in nested tracing

[hinthornw]

No description provided.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Project	Deployment	Preview	Comments	Updated (UTC)
langchain	⬜️ Ignored	Preview		Aug 11, 2025 10:39pm

[codspeed-hq]

CodSpeed WallTime Performance Report

Merging #31986 will not alter performance

_{Comparing wfh/honor_context (3e3f8ba) with master (166c027)}

⚠️ Unknown Walltime execution environment detected

Using the Walltime instrument on standard Hosted Runners will lead to inconsistent data.

For the most accurate results, we recommend using CodSpeed Macro Runners: bare-metal machines fine-tuned for performance measurement consistency.

Summary

✅ 13 untouched benchmarks

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #31986 will not alter performance

_{Comparing wfh/honor_context (3e3f8ba) with master (166c027)}

Summary

✅ 14 untouched benchmarks

[Copilot]

Pull Request Overview

This PR fixes a bug where the enabled=false parameter in nested tracing contexts was not being properly honored, allowing traces to be persisted when they should have been disabled.

Key changes:

• Updated the LangSmithTracer to check tracing context enablement state and mark runs as disabled
• Added early returns in persistence methods to skip disabled runs
• Enhanced test coverage to verify nested tracing behavior with disabled contexts

Reviewed Changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated no comments.

File	Description
libs/core/langchain_core/tracers/langchain.py	Implements the core fix by checking tracing context state and skipping persistence for disabled runs
libs/core/tests/unit_tests/runnables/test_tracing_interops.py	Adds test case to verify nested tracing with disabled context works correctly