Mark Backman
Mark Backman
> I was thinking: we're using uv to run our python script. That shouldn't have an impact.
@chadbailey59 is this still an issue?
@JulianGerhard21 I can confirm what you're seeing, but I'm not sure what the intended behavior is. I'll have to ask @aconchillo. Essentially 100% of Pipecat interactions run with interruptions enabled....
cc @vipyne who has worked with MCP and may have an idea. @vipyne my hunch is that the MCP call never returns, which is what results in the dangling task...
We're looking into MCP now. I did hit this in testing over the weekend, so it might be something in our MCPClient. We'll know soon.
I'm tagging @vipyne as she's more up to date on MCP things than I am. @vipyne, @Raphyo is seeing a dangling task when calling an MCP tool. I know you...
Apologies for letting this go for so long. These issues have since been resolved, so I'm closing out this contribution.
What issue are we trying to solve? Is it that the TTSSpeakFrames aren't added to the context?
@aconchillo should we close this one?
Closing this as enough things in the aggregators have changed.