Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Restore the Azure Foundry calendar sample's compatibility with the
a2a-sdk==1.1.2already selected by its lockfile. The executor, server, and example client still used removed 0.3 APIs, so the locked installation could not start.Relates to #462. This updates only
samples/python/agents/azureaifoundry_sdk/azurefoundryagent, not the other Python samples.Changes
a2a-sdk>=1.1.2,<2.0, add twelve credential-free regression tests, and document setup and limitations.The Azure backend is unchanged. This is not a migration to Azure AI Projects 2.x or the Responses API. Every resolved package version remains unchanged, including
azure-ai-agents==1.0.0andazure-ai-projects==1.0.0b11.Proof of the fix
Before
Running the new regression suite against the original sample at
1d7b7be24971c60fe5019182c1d26b7e9ae137ed, with its locked dependencies installed, produces twelve errors. The first executor import fails before making an Azure request:After
From the sample directory:
uv sync --locked --python 3.12 uv run --python 3.12 --no-sync --with pytest==9.0.2 python -m pytest -q .The tests exercise the real A2A SDK and in-process HTTP routes, mocking only the Foundry agent behavior. Coverage includes imports, server configuration, health and card discovery, protobuf parts, task-event order and correlation, context isolation/reuse, exceptions, cancellation rejection, and the complete example client in both messaging modes.
Additional local checks passed:
git diff --check.The tests can also run without pytest:
Real Azure validation
Tested on November 16, 2026 using GPT-5 mini
2025-08-07, Global Standard, East US 2, through the existing classic Agents API.check_availabilityandget_upcoming_eventsProvider terminal states and usage were checked, rather than treating HTTP 200 or response text as proof of completion. The broad availability questions in the example client prompted clarification, so the additional request supplied exact UTC timestamps to exercise the availability tool.
The calendar functions remain simulated. This did not access an Outlook calendar. No credentials, account identifiers, or raw authenticated logs are included.
Scope and limitations
The classic Azure calls and polling remain synchronous. Cancellation, automatic cleanup on server shutdown, and durable conversation storage are not implemented. Full monorepo tests and other Azure model configurations were not validated.
CI
Both upstream workflow jobs passed for
3a2c10fa0dff4f05fca4548e15ed7a6647d526e6:Lint Code Base.
Lint Go.
Follow the CONTRIBUTING guide.