Timon Vonk

> In implementing this, intuitively there's likely a solution that isn't write only like tracing events. E.g. the concept of a notification stream, or work stream which has a defined...

The ids are also used as unique identifiers for both the cache and (most) databases.

One of the things with nodes I really would like to do, is have them be generic over the datatype they carry (for multi modal). I think that combines really...

> Yeah, perhaps splitting the id you currently have into assigned id (e.g. a v7 uuid) and a calculated cache key (perhaps just a hash, no uuid) could be worth...

Thanks, this very helpful, I'll check it out when I have time

Fixed by adding the env variable and manually pulling the image before the build. Also upgraded to 0.19, but I recon the eager pull fixed it. Thanks for the help!

Actually, #413 would be a nice extension to this

@64bit My approach here still feels a bit like a hack. EventSource I feel is the real challenge here, perhaps replacing that or otherwise provides a more robust solution. For...

Agree would be nice to have this more flexible. `async_openai` already implements backoff, https://docs.rs/async-openai/latest/async_openai/struct.Client.html#method.with_backoff. We could certainly provide a nicer api for it, with 3.5 it's, unless you're max tier,...

@tinco `backoff` has a builder https://docs.rs/backoff/0.4.0/backoff/exponential/struct.ExponentialBackoffBuilder.html