-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Closed
Labels
AI AgentsAI ProjectsClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Description
- Package Name: azure.ai.projects.aio
- Package Version: 1.0.0
- Operating System: Linux
- Python Version: 3.12.0
Describe the bug
When calling agents_client.messages.list(thread_id=thread_id, limit=limit)
, the limit parameter is not taken into consideration. I can set any value; it returns all the conversations (I haven't tried it with one that is over 100 messages).
To Reproduce
Steps to reproduce the behavior:
- Set limit to 10
- call agents_client.messages.list(thread_id=thread_id, limit=limit) with valid thread_id
- receive back messages
- Check the number of messages
Expected behavior
The returned number of messages should be limited to the set value
Additional context
It should work as described in the docs -> https://learn.microsoft.com/en-us/python/api/azure-ai-agents/azure.ai.agents.operations.messagesoperations?view=azure-python-preview#azure-ai-agents-operations-messagesoperations-list
Metadata
Metadata
Assignees
Labels
AI AgentsAI ProjectsClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that