Skip to content

Fix response history limit ordering - #48602

Closed
Shiva S (Shivakishore14) wants to merge 4 commits into
Azure:mainfrom
Shivakishore14:fix/issue-48514-history-limit
Closed

Shiva S (Shivakishore14) wants to merge 4 commits into
Azure:mainfrom
Shivakishore14:fix/issue-48514-history-limit

Conversation

@Shivakishore14

Copy link
Copy Markdown
Member

Fixes #48514

Description

  • retain the newest history item IDs when in-memory and file-backed response providers apply a limit
  • update provider parity tests to assert chronological tail truncation
  • document the fix in the package changelog

The Foundry provider is unchanged because it forwards limit to the Foundry history endpoint and does not truncate a local resolved list.

Testing

  • python -m pytest tests/unit/test_in_memory_provider_crud.py tests/unit/test_file_response_store_parity.py -q

@github-actions github-actions Bot added the Hosted Agents sdk/agentserver/* label Aug 17, 2026
@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
9 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

Retain the newest history items when local response providers apply a limit, and add regression coverage for both in-memory and file-backed storage.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Shivakishore14
Shiva S (Shivakishore14) force-pushed the fix/issue-48514-history-limit branch from 9571af8 to e74ca94 Compare August 19, 2026 09:20
Move the history limit fix into a new unreleased changelog section and bump the package version.\n\nCo-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@Shivakishore14

Copy link
Copy Markdown
Member Author

Duplicate of #48560 , closing this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Hosted Agents sdk/agentserver/*

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[azure-ai-agentserver-responses] get_history_item_ids uses resolved[:limit] — truncates newest history instead of oldest

1 participant