Repository navigation
fix: publish terminal task state to subscriber streams (#1175) #1191
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
anthonyrs06
wants to merge
1
commit into
a2aproject:main
Choose a base branch
from
anthonyrs06:fix/1175-publish-terminal-to-subscribers
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
_persist_and_publish_terminal is called after await self._is_finished.wait() -> the producer's finally closes the subscriber queue -> await self._event_queue_subscribers.enqueue_event (line 932) -> logs a WARNING each time
Should we have here publish_to_stream=False?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I independently checked this fallback with a real
TaskManager/InMemoryTaskStore, the real event queues, and a fake push sender. Your suggestedpublish_to_stream=Falseremoves the warning while preserving the cancellation outcome.At PR head
6e9144edf885ae1f8ec1cc6afa5cbfc119187ca0, after the fake executor exits withCancelledErrorand the subscriber finishes, callingActiveTask.cancel()gives:CANCELED;CANCELEDnotification;Queue was closed during enqueuing. Event dropped.warning.Adding the flag only to the post-wait fallback removes that warning. A live-producer control still receives one
CANCELEDstream event and one fake push, so the live publication path remains exercised.This confirms a dropped stream publication attempt; the stored cancellation and fake push call are retained. I did not use HTTP, a model, or real push delivery. The test reaches the finished state through the executor/consumer lifecycle; it does not set private flags or replace queue behavior.
With only that one-line source change, repository lint exits 0 and the full suite reports 1988 passed, 90 skipped, 3 xfailed, 1 xpassed (Python 3.12.11, locked development environment). The separate two-case fixture below also passes.
Two-case local regression
Save as
test_cancel_fallback.pyand runpython -m pytest -q -s test_cancel_fallback.pyin an SDK environment (Python 3.12.11 used here).Disclosure: Mission, with Codex assistance. This adds regression evidence for @mykytanetipa’s suggestion, also confirmed by @astrogilda, on @anthonyrs06’s existing patch.