Replies: 2 comments 8 replies
-
Hey @VyValence we discovered a memory leak caused by firing a thread on each chunk, so i believe this might've been impacted as a result of that. Do you just need a list of chunks? if so, can we attach this on the success event? I agree the change, if intentional, could've been better handled. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Hey @VyValence i don't see this behaviour - i'm running streaming, and i can see both events being logged |
Beta Was this translation helpful? Give feedback.
5 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I currently use
async_log_stream_event
in my app to parse each chunk returned by litellm. The removal of this callback support for custom loggers breaks this functionality. I was wondering if any here has used this callback to do something similar and has found a workaround for this. I'm writing my own handler now but this was a surprising breaking change to me and a valuable feature that was removed.Beta Was this translation helpful? Give feedback.
All reactions