fix(langchain): use get_buffer_string for message summarization
#34607
+88
−12
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.
Fixes #34517
Supersedes #34557, #34570
Fixes token inflation in
SummarizationMiddlewarethat caused context window overflow during summarization.Root cause: When formatting messages for the summary prompt,
str(messages)was implicitly called, which includes all Pydantic metadata fields (usage_metadata,response_metadata,additional_kwargs, etc.). This caused the stringified representation to use ~2.5x more tokens thancount_tokens_approximatelyestimates.Problem:
count_tokens_approximatelystr(messages)in the prompt uses 2.5x more tokensContextLengthExceededFix: Use
get_buffer_string()to format messages, which produces compact output:Instead of verbose Pydantic repr: