Back

langchain #35031

fix(core): handle None content in ToolMessageChunk merge

by Mr-Neutr0n · Feb 06, 2026 at 19:30 UTC · scan-b1984cc9f35c4d6d

Medium Risk (25%)

Get this automatically on every PR

Install the Axiomo GitHub App to get Signals as check runs and PR comments on every pull request.

Install App

Risk Assessment

Risk level: Medium (25%)

Risk Drivers

  • new_contributor: First contribution from MrNeutron

Intent

2/2 criteria met

Ensure ToolMessageChunk merge handles None content correctly.

Non-Goals

  • - Refactor merging process
  • - Add new features
  • - Optimize performance

Acceptance Criteria

  • Merging ToolMessageChunk with None content results in None.

    Added early return when content is None in tool.py.

  • Prevent 'NoneNone' string when merging.

    Return ensures content is not coerced to 'None'.

Confidence: 90.0% Source: pr description AI: openai

Contributors

Mr-Neutr0n PR Author ? Low Trust
Account Age: 2108 days
Prior PRs: 2
Merged: 1

Has 1 merged PRs to this repo. maintains 79 public repositories. unfamiliar with libs/core/langchain_core/messages/tool.py.

MrNeutron 2 commits ? New Contributor
Account Age: 4649 days
Prior PRs: 0

First-time contributor to this repository.

Evidence

Evidence Completeness: 80.0%
ci_passing Passing
tests_passing Passing
build_successful Passing
lint_passing Passing
Missing: security_scan_clean, coverage_maintained

Supply Chain

None Risk
Modifies dependencies
Modifies lockfile
Modifies CI config
Modifies build scripts

Focus Files

Review 1 file(s)

libs/core/langchain_core/messages/tool.py +4

Source code

medium

Triage

7

minutes to review

low

effort level

none

staleness risk

Standard review process

Recommendation

COMMENT 70.0% readiness

Some concerns to address before approval

Next Steps

Question

Why is security_scan_clean missing? Consider adding this check.

Question

Why is coverage_maintained missing? Consider adding this check.