-
Notifications
You must be signed in to change notification settings - Fork 94
Implement ClientIO interaction support on Agent-Server #2178
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
Merged
Merged
Changes from 13 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
5316bbd
Add initial config persistence design to agentServerSessions.md
GeorgeNgMsft 5d40c35
Add design doc for async ClientIO callbacks in agent-server
GeorgeNgMsft 2aa8f54
Implement async deferred-promise pattern for blocking ClientIO callba…
GeorgeNgMsft dfff4c7
Merge branch 'main' into dev/georgeng/async-clientio-callbacks
GeorgeNgMsft 680bcb6
Merge branch 'main' into dev/georgeng/async-clientio-callbacks
GeorgeNgMsft 8316fd5
Update documentation
GeorgeNgMsft 3c04335
Merge branch 'dev/georgeng/async-clientio-callbacks' of https://githu…
GeorgeNgMsft 43c7091
Update documentation and tests
GeorgeNgMsft b818baf
Add clientIO timeout in edgecase where no valid clients/no clients + …
GeorgeNgMsft fe299c9
Address comments for cancellation clarity and logging
GeorgeNgMsft b28f861
Merge branch 'main' into dev/georgeng/async-clientio-callbacks
GeorgeNgMsft 94b4766
Fix build
GeorgeNgMsft cc4ac42
Merge branch 'dev/georgeng/async-clientio-callbacks' of https://githu…
GeorgeNgMsft 1a908ad
Address clients and update document
GeorgeNgMsft 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
Large diffs are not rendered by default.
Oops, something went wrong.
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
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
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.
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.
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.
Doesn't the display log replay sufficient?
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.
Technically, you could retrieve the last question asked from the previous message in display log. However, that's adding additional (potentially fragile) extraction logic on an ordered stream of events. In addition, potential future capabilities like interruptions or moving operations into the background could make extracting from display log much more difficult.
I think it's cleaner to just store pending interactions in this array (which is also already filtered for the specific connection). No need to run any parsing logic.