Marc Torrellas Socastro
Marc Torrellas Socastro
@davidzhao using this issue for a similar topic. I'm seeing ``` 2025-09-02 22:24:28,757 - DEBUG livekit.agents - job exiting | extras: reason=, tid=19139364, job_id=simulated-job-b5a91f075e59 {"reason": "", "tid": 19139364, "job_id": "simulated-job-b5a91f075e59"}...
I'm trying to build something like that too! If there are any examples available, please share
also interested in this. If someone could drop some code or more hints, I'd really appreciate
FYI, I found this "solution" ``` for name, field in model.__class__.model_fields.items(): key = field.alias if by_alias and field.alias else name result[key] = getattr(model, name) ``` Not super clean, but works...
can I get some feedback here? e.g. @potter-potter @rbiseck3 (sorry for the spam, feel free to share with whoever that could help)
Hi @potter-potter, I fixed the conflicts. Could you enable CI at least?
> Hi @marctorsoc I'm not sure this metadata is of general interest for users of the library. Let me ask around and see what folks have to say. > >...
Seeing this again since the update to 3.1 from 2.1.18. All traces have the same session_id. But for some reason, a new trace is created for every interaction (LLM response,...
Hi @tinalenguyen , thanks for your answer. Understood so for the case where I use a tool that does session.say the formula should be ``` total_latency = eou.end_of_utterance_delay + llm.time_to_last_token...
That's great @tinalenguyen ,but I actually want the individual components too so I understand what needs to be improved (turn detection, stt, llm or tts)