Closed MSDNAndi closed 2 days ago
@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.
@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:
Describe the bug The test run in testrunner Step04_AgentOrchestration fails
To Reproduce Steps to reproduce the behavior:
Screenshots If applicable, add screenshots to help explain your problem.
Platform
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