Skip to content

.Net Agent Runtime Fix: Allow multiple subscribers to handle events concurrently#12713

Merged
crickman merged 2 commits intomainfrom
fix_concurrent_events
Jul 15, 2025
Merged

.Net Agent Runtime Fix: Allow multiple subscribers to handle events concurrently#12713
crickman merged 2 commits intomainfrom
fix_concurrent_events

Conversation

@crickman
Copy link
Copy Markdown
Contributor

@crickman crickman commented Jul 14, 2025

Motivation and Context

Enable multiple subscribers to to handle events concurrently (instead of sequentially)

Fixes: #12701

Description

The event handling loop of the InProcessRuntime is waiting on each subscriber to handle the event. This conflicts with performance expectations.

Contribution Checklist

@crickman crickman self-assigned this Jul 14, 2025
@crickman crickman requested a review from a team as a code owner July 14, 2025 22:33
@crickman crickman added bug Something isn't working agents labels Jul 14, 2025
@crickman crickman moved this to Sprint: In Review in Semantic Kernel Jul 14, 2025
@moonbox3 moonbox3 added the .NET Issue or Pull requests regarding .NET code label Jul 14, 2025
@github-actions github-actions Bot changed the title .NET Agent Runtime Fix: Allow multiple subscribers to handle events concurrently .Net Agent Runtime Fix: Allow multiple subscribers to handle events concurrently Jul 14, 2025
@crickman crickman enabled auto-merge July 15, 2025 15:21
@crickman crickman added this pull request to the merge queue Jul 15, 2025
Merged via the queue into main with commit d0fed70 Jul 15, 2025
19 checks passed
@crickman crickman deleted the fix_concurrent_events branch July 15, 2025 16:59
@github-project-automation github-project-automation Bot moved this from Sprint: In Review to Sprint: Done in Semantic Kernel Jul 15, 2025
jcruzmot-te pushed a commit to thousandeyes/aia-semantic-kernel that referenced this pull request Sep 15, 2025
…oncurrently (microsoft#12713)

### Motivation and Context
<!-- Thank you for your contribution to the semantic-kernel repo!
Please help reviewers and future users, providing the following
information:
  1. Why is this change required?
  2. What problem does it solve?
  3. What scenario does it contribute to?
  4. If it fixes an open issue, please link to the issue here.
-->

Enable multiple subscribers to to handle events concurrently (instead of
sequentially)

Fixes: microsoft#12701

### Description
<!-- Describe your changes, the overall approach, the underlying design.
These notes will help understanding how your code works. Thanks! -->

The event handling loop of the `InProcessRuntime` is waiting on each
subscriber to handle the event. This conflicts with performance
expectations.

### Contribution Checklist
<!-- Before submitting this PR, please make sure: -->

- [X] The code builds clean without any errors or warnings
- [X] The PR follows the [SK Contribution
Guidelines](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md)
and the [pre-submission formatting
script](https://github.com/microsoft/semantic-kernel/blob/main/CONTRIBUTING.md#development-scripts)
raises no violations
- [X] All unit tests pass, and I have added new tests where possible
- [X] I didn't break anyone 😄
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agents bug Something isn't working .NET Issue or Pull requests regarding .NET code

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

.Net: Bug: ConcurrentOrchestration collects responses sequentially from all agents

4 participants