Python: extract_range(preserve_pairs=True) reorders messages around a call/result pair (fix open as PR #14165, unlinked)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 25/100
Research direction
Start in python/semantic_kernel/contents/history_reducer/chat_history_reducer_utils.py at extract_range() and run the provided reproduction with preserve_pairs=True. Confirm that an interleaved message remains between the call and result in the extracted history, then add or update regression coverage so the extracted order matches the original history.
Written by the indexing model from the issue text.
Description
Describe the bug
extract_range() in python/semantic_kernel/contents/history_reducer/chat_history_reducer_utils.py (used by ChatHistorySummarizationReducer with preserve_pairs=True) scrambles the chronological order of the extracted messages whenever a function-call/result pair has other messages interleaved between them.
Current main:
extracted: list[ChatMessageContent] = []
i = 0
while i < len(sliced):
idx = sliced[i]
msg = history[idx]
...
if preserve_pairs and idx in pair_map:
paired_idx = pair_map[idx]
if start <= paired_idx < end:
...
extracted.append(msg)
if paired_idx > idx:
extracted.append(history[paired_idx])
if paired_idx in sliced:
sliced.remove(paired_idx)
...
When the loop reaches the earlier half of a pair (the call), it immediately appends the later half (the result) right behind it in extracted, then removes the result's index from sliced so it isn't visited again at its natural position. That is what moves the result out of its original place whenever anything sits between the call and the result.
To Reproduce
Ran against the actual installed semantic-kernel package (1.44.1; chat_history_reducer_utils.py confirmed byte-identical to the current main file before running):
from semantic_kernel.contents.chat_message_content import ChatMessageContent
from semantic_kernel.contents.function_call_content import FunctionCallContent
from semantic_kernel.contents.function_result_content import FunctionResultContent
from semantic_kernel.contents.utils.author_role import AuthorRole
from semantic_kernel.contents.history_reducer.chat_history_reducer_utils import extract_range
msg0 = ChatMessageContent(role=AuthorRole.USER, content="What's the weather in Paris and Tokyo?")
msg1 = ChatMessageContent(role=AuthorRole.ASSISTANT, items=[FunctionCallContent(id="call_paris", name="get_weather")])
msg2 = ChatMessageContent(role=AuthorRole.USER, content="also check the forecast for tomorrow")
msg3 = ChatMessageContent(role=AuthorRole.TOOL, items=[FunctionResultContent(id="call_paris", name="get_weather", result="15C")])
msg4 = ChatMessageContent(role=AuthorRole.ASSISTANT, content="Paris is 15C.")
history = [msg0, msg1, msg2, msg3, msg4]
out = extract_range(history, start=0, end=5, preserve_pairs=True)
for m in out:
print(m.role, m.content or [getattr(it, "id", None) for it in m.items])
Output:
AuthorRole.USER What's the weather in Paris and Tokyo?
AuthorRole.ASSISTANT ['call_paris']
AuthorRole.TOOL ['call_paris']
AuthorRole.USER also check the forecast for tomorrow
AuthorRole.ASSISTANT Paris is 15C.
The tool result (originally index 3, after the interleaved user message at index 2) is pulled forward to sit right after the call, and the interleaved user message is pushed after it - the extracted order no longer matches history[0:5].
Expected behavior
extract_range(history, 0, 5, preserve_pairs=True) should return the messages in their original order (minus anything actually filtered out), i.e. history[0], history[1], history[2], history[3], history[4] unchanged, since nothing here should be filtered.
Platform
- Language: Python
- Source: pip package
semantic-kernel==1.44.1, confirmed unchanged on currentmain - File:
python/semantic_kernel/contents/history_reducer/chat_history_reducer_utils.py, functionextract_range()
Additional context
There is already an open, unmerged fix for exactly this for this: PR #14165 ("Python: Fix extract_range reordering messages when preserving function call/result pairs"), open since 2026-07-18, which rewrites the loop as a single forward pass so messages are never moved out of position. It has no linked issue, which may be why it has sat without a maintainer review beyond the automated Copilot pass. Filing this so the fix has something to attach to.
Note: while reviewing that PR's diff I found the rewritten version still shares the same pair_map[cidx] = ridx construction as current main, which has a separate, still-open dict-collision problem when a call message contains more than one function call (multiple results mapping to the same call index) - reported separately since it's a distinct bug from this ordering issue and reproduces on both the current code and PR #14165's rewrite.
- Dominant language
- C#
- Stars
- 28.8k
- Forks
- 4.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 48
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/semantic-kernel
-
Python: Bug: ChatMessageContent.from_element drops AudioContent and BinaryContent into raw TextContentPossibly taken @halcyon-past claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/semantic-kernel#14824 · 1 comment ·
Maintainers usually reply within 3 days
-
Python: Bug: Redis search returns None for every field that declares a storage_name, because RETURN lists the declared namePossibly taken @wasim-builds claimed this 9 days ago. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/semantic-kernel#14753 · 1 comment ·
Maintainers usually reply within 3 days
-
.Net: gpt-image-1 is the default image model in the .NET OpenAI connector, and OpenAI shuts it down on October 23Possibly taken @nightcityblade claimed this 46 days ago. Open.NET triage
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/semantic-kernel#14526 · 1 comment ·
Maintainers usually reply within 3 days
-
Python: VolatileMemoryStore.get_batch and get_nearest_matches ignore with_embeddings=False (deepcopy result is discarded)Possibly taken @VANDRANKI claimed this 48 days ago. Openpython triage
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/semantic-kernel#14522 ·
Maintainers usually reply within 3 days
-
.Net: Bug: BinaryContent does not decode the %xx escapes of a non-base64 data URIPossibly taken @Laurianti claimed this 48 days ago. Open.NET triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
microsoft/semantic-kernel#14518 ·
Maintainers usually reply within 3 days
All issues in microsoft/semantic-kernel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Support Flux ignore rules (drift detection ignore paths) in Microsoft.KubernetesConfiguration schemaOpen
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Azure/azure-resource-manager-schemas#3921 ·
Maintainers usually reply within 1 day
-
text-align: justify is ignored in HTML to PDF conversionPossibly taken @PrzemyslawKlys claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
asyncapi/modelina#2709 · 1 comment ·
Maintainers usually reply within 1 day