-
Notifications
You must be signed in to change notification settings - Fork 450
Comparing changes
Open a pull request
base repository: a2aproject/a2a-python
base: v0.2.15
head repository: a2aproject/a2a-python
compare: v0.2.16
- 6 commits
- 60 files changed
- 5 contributors
Commits on Jul 21, 2025
-
ci: Remove noxfile and add shell script for formatting (#331)
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 0756d23 - Browse repository at this point
Copy the full SHA 0756d23View commit details -
test: Add missing tests for reject method (#328)
# Description This update addresses the need to improve test coverage for the `reject` method in `TaskUpdater`. While basic tests for the `reject` method already existed, this PR adds a crucial test case to handle race conditions, ensuring the reliability and robustness of the task rejection functionality. **Changes:** * Added `test_reject_concurrently_with_complete` to `tests/server/tasks/test_task_updater.py`. This test simulates a race condition by calling `reject()` and `complete()` concurrently on the same task. * It verifies that only one of the terminal state updates succeeds and that only one event is sent, preventing inconsistent states. **Value:** * Improves test coverage by testing for race conditions. * Ensures the reliability and consistency of the `TaskUpdater` when multiple terminal state updates are attempted simultaneously.
Configuration menu - View commit details
-
Copy full SHA for 0e9baaa - Browse repository at this point
Copy the full SHA 0e9baaaView commit details -
fix: client should not specify
taskIdif it doesn't exist (#264)# Description I'm submitting this PR as a proposal based off of #218 (comment). If the taskId doesn't exist, I was thinking that an exception should be thrown to prevent the client from specifying the id. The reason I think this change is required because if the client specifies a taskId but one doesn't exist, it won't actually get push notifications based off that first request, because the logic to `set_info()` gets skipped because there is no `task` when _setup_message_execution is called. Found while working on mozilla-ai/any-agent#414
Configuration menu - View commit details
-
Copy full SHA for 97f1093 - Browse repository at this point
Copy the full SHA 97f1093View commit details -
feat: Convert fields in
types.pyto usesnake_case(#199)Makes types more pythonic Pydantic aliases can be used for initialization and are used automatically for serialization. Added a workaround to support `camelCase` when setting specific attributes. NOTE: In 0.3.0 and later, only snake_case will be supported for direct attribute access.
Configuration menu - View commit details
-
Copy full SHA for 0bb5563 - Browse repository at this point
Copy the full SHA 0bb5563View commit details -
Configuration menu - View commit details
-
Copy full SHA for f22b384 - Browse repository at this point
Copy the full SHA f22b384View commit details -
chore(main): release 0.2.16 (#332)
🤖 I have created a release *beep* *boop* --- ## [0.2.16](v0.2.15...v0.2.16) (2025-07-21) ### Features * Convert fields in `types.py` to use `snake_case` ([#199](#199)) ([0bb5563](0bb5563)) ### Bug Fixes * Add deprecation warning for camelCase alias ([#334](#334)) ([f22b384](f22b384)) * client should not specify `taskId` if it doesn't exist ([#264](#264)) ([97f1093](97f1093)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for e52273d - Browse repository at this point
Copy the full SHA e52273dView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v0.2.15...v0.2.16