Fix language: binary data is replaced with placeholders, not truncated

This commit is contained in:
Paul Kompfner
2026-04-11 14:39:25 -04:00
parent 1a02b5d61a
commit e38647151d
2 changed files with 5 additions and 5 deletions

View File

@@ -1 +1 @@
- Added `truncate_large_values` parameter to `LLMContext.get_messages()`. When `True`, returns compact deep copies of messages with binary data (base64 images, audio) fully truncated and long string values in LLM-specific messages recursively truncated. Useful for serialization, logging, and debugging tools.
- Added `truncate_large_values` parameter to `LLMContext.get_messages()`. When `True`, returns compact deep copies of messages with binary data (base64 images, audio) replaced by short placeholders and long string values in LLM-specific messages recursively truncated. Useful for serialization, logging, and debugging tools.

View File

@@ -214,9 +214,9 @@ class LLMContext:
logged; this is intended to catch accidental use of
incompatible LLM-specific messages.
truncate_large_values: If True, return deep copies of messages with
large values replaced by short placeholders. For standard
messages, known binary data (base64-encoded images, audio) is
fully truncated. For LLM-specific messages, long string values
large values shortened. For standard messages, known binary
data (base64-encoded images, audio) is replaced with short
placeholders. For LLM-specific messages, long string values
are truncated.
Returns:
@@ -247,7 +247,7 @@ class LLMContext:
"""Return deep copies of messages with large values replaced by placeholders.
For standard (universal-format) messages, the following known binary
patterns are fully truncated:
patterns are replaced with short placeholders:
- ``image_url`` items with ``data:image/...`` base64 URLs
- ``input_audio`` items with ``input_audio.data`` or ``audio`` fields