Skip to content
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.

Sign up for GitHub

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

Jump to bottom

.Net: Bug: GettingStartedWithProcesses Step04_AgentOrchestration: System.InvalidOperationException : A message targeting function 'RenderError' has resulted in a function named 'RenderDone' becoming invocable. Are the function names configured correctly? #9778

Closed
MSDNAndi opened this issue Nov 21, 2024 · 2 comments · Fixed by #9797
Closed

.Net: Bug: GettingStartedWithProcesses Step04_AgentOrchestration: System.InvalidOperationException : A message targeting function 'RenderError' has resulted in a function named 'RenderDone' becoming invocable. Are the function names configured correctly? #9778

MSDNAndi opened this issue Nov 21, 2024 · 2 comments · Fixed by #9797
Assignees
@crickman
Labels
bug Something isn't working experimental Associated with an experimental feature .NET Issue or Pull requests regarding .NET code processes

Comments

@MSDNAndi
Copy link

Describe the bug
The test run in testrunner Step04_AgentOrchestration fails

To Reproduce
Steps to reproduce the behavior:

  1. Load Project
  2. Configure secrets
  3. Run tests
    Expected behavior
    Test should complete without failure

Screenshots
If applicable, add screenshots to help explain your problem.

Platform

  • OS: Windows 11
  • IDE: VS2022
  • Language: C#
  • Source: main branch of repository

Additional context
 Step04.Step04_AgentOrchestration.DelegatedGroupChatAsync
 Source: Step04_AgentOrchestration.cs line 32
 Duration: 432 ms

Message: 
System.InvalidOperationException : A message targeting function 'RenderError' has resulted in a function named 'RenderDone' becoming invocable. Are the function names configured correctly?

Stack Trace: 
LocalStep.HandleMessageAsync(ProcessMessage message) line 182
LocalProcess.Internal_ExecuteAsync(Kernel kernel, Int32 maxSupersteps, Boolean keepAlive, CancellationToken cancellationToken) line 286
LocalProcess.RunOnceAsync(KernelProcessEvent processEvent, Kernel kernel) line 85
LocalKernelProcessFactory.StartAsync(KernelProcess process, Kernel kernel, KernelProcessEvent initialEvent) line 24
Step04_AgentOrchestration.RunProcessAsync(KernelProcess process) line 68
Step04_AgentOrchestration.DelegatedGroupChatAsync() line 38
--- End of stack trace from previous location ---

Standard Output: 
USER: Hi
[00:00] USER: Hi
@MSDNAndi MSDNAndi added the bug Something isn't working label Nov 21, 2024
@markwallace-microsoft markwallace-microsoft added .NET Issue or Pull requests regarding .NET code triage labels Nov 21, 2024
@github-actions github-actions bot changed the title Bug: GettingStartedWithProcesses Step04_AgentOrchestration: System.InvalidOperationException : A message targeting function 'RenderError' has resulted in a function named 'RenderDone' becoming invocable. Are the function names configured correctly? .Net: Bug: GettingStartedWithProcesses Step04_AgentOrchestration: System.InvalidOperationException : A message targeting function 'RenderError' has resulted in a function named 'RenderDone' becoming invocable. Are the function names configured correctly? Nov 21, 2024
@crickman crickman added processes experimental Associated with an experimental feature labels Nov 22, 2024
@crickman crickman moved this from Bug to Sprint: In Progress in Semantic Kernel Nov 22, 2024
@crickman crickman added question Further information is requested wontfix This will not be worked on labels Nov 22, 2024
@crickman crickman moved this from Sprint: In Progress to Sprint: In Review in Semantic Kernel Nov 22, 2024
@crickman crickman removed question Further information is requested wontfix This will not be worked on labels Nov 22, 2024
@crickman crickman moved this from Sprint: In Review to Sprint: In Progress in Semantic Kernel Nov 22, 2024
@crickman
Copy link
Contributor

@MSDNAndi - Thank you for reporting this issue. The Process Framework has undergone rapid changes over the past serveral weeks as part of its early evolution. I will certainly evaluate and rectify this sample.

@crickman
Copy link
Contributor

crickman commented Nov 22, 2024 •
edited
Loading

@MSDNAndi - I repeatedly ran this sample until failure...on the 10th try I was able to reproduce this exception. The issue has to do with the function parameter name for RenderError being out-of-sync. I have published a fix that you can apply locally until it is approved and merged:

#9797

@crickman crickman mentioned this issue Nov 22, 2024
Merged
4 tasks
github-merge-queue bot pushed a commit that referenced this issue Nov 23, 2024
@crickman
.Net Processes - Sync parameter name for error handler (#9797)
5ae74d7 
### 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.
-->

Update sample `Step04_AgentOrchestration` to correctly specify the name
of the function parameter.

Fixes: #9778

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

Sample specified parameter name `exception` but the actual name had been
refactored to `error`.

### 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 😄
@github-project-automation github-project-automation bot moved this from Sprint: In Progress to Sprint: Done in Semantic Kernel Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@crickman crickman

Labels
bug Something isn't working experimental Associated with an experimental feature .NET Issue or Pull requests regarding .NET code processes
Projects
Semantic Kernel
Status: Sprint: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

.Net Processes - Sync parameter name for error handler microsoft/semantic-kernel
3 participants
@MSDNAndi @crickman @markwallace-microsoft