Dmytro Struk
Dmytro Struk
> may I ask how to test unit test cases locally @N-E-W-T-O-N ```bash cd dotnet/src/Connectors/Connectors.HuggingFace.UnitTests dotnet test ```
> The issue is unit tests are still based on the previous version of embedding dimensions as noted by@RogerBarreto .Would you like me to update the unit test accordingly? @N-E-W-T-O-N...
> @dmytrostruk anything to add from my side @N-E-W-T-O-N I think we are ready to merge this to `main`. I added a couple of small fixes to the example. Thanks...
@N-E-W-T-O-N Thank you for contribution!
> Do we have a right way to see a prompt is actually sent to the azure open ai instead of checking chat history message? I have the same issue...
Yes, `MemoryBuilder` will be revised as part of global memory-related refactoring. There could be a solution, where `MemoryBuilder` won't be needed at all and we will register all memory-related services...
Closing this issue, as DI work will be done in scope of each separate memory connector.
> I think the Google connector also supports function calling @markwallace-microsoft Good point. But auto function invocation filter is not invoked for Google connector at the moment. Initial idea was...
@franklinlindemberg Thanks for reporting this issue! Could you please try to use automatic function calling instead of `FunctionCallingStepwisePlanner` and see if you can reproduce the problem? We recommend automatic function...
@franklinlindemberg It would be great to learn about your experience using automatic function calling and if you can reproduce this issue with it. As for now, I'm going to close...