Christophe Bornet
Christophe Bornet
Note that this also reduces the isolation between the agents. Tradeoffs.
We could also have regular (once-per-day?) checks that those examples run correctly. Currently it would be slow and hard to write tests that run on every PR for all the...
I think it's better to keep a mono-repo. A multi-repo will quickly lead to a dependency hell. We should find other ways to solve the problems you describe.
Will older versions of openai
Currently `fastapi` is a dependency of both the server and the client: ``` python -m venv /tmp/venv source /tmp/venv/bin/activate pip install "langserve[client]" python >>> from langserve import RemoteRunnable Traceback (most...
For Mutiny, that would be something like (on master): ```java Multi messages = ... Multi sendResults = Multi.createFrom().publisher(sender.sendMany(messageSpecs)); MessageSpec message = ... Uni messageId = Uni.createFrom().publisher(sender.sendOne(messageSpec)); ```
Discussed with @lhotari : we already depend on `pulsar-client-api` for a variety of classes (Message, MessageId, ...). So we can probably reuse the PulsarException classes, even when we'll do the...
Beware that batched messages may not be acked if all the messages from the batch are not acked before closing the consumer (the consumer is closed when consumeOne/consumeMany completes).
> This is most likely caused by the lack of configuring .batchIndexAckEnabled(true) on the ReactiveMessageConsumerBuilder and enabling acknowledgmentAtBatchIndexLevelEnabled=true in broker.conf I think that if the consumer gets closed the batch...