RabbitMQ stream-based client for Scala built on top of Fs2 and Cats Effect -> https://fs2-rabbit.profunktor.dev/
but to test it, I need rabbit to fail
which I can't figure out how to make happen programatically
so I want to pass a wrapped connection that fails randomly
I don't know what I'm doing in terms of release management but I don't mind contributing in general
@gvolpe the examples link on this page: https://fs2-rabbit.profunktor.dev/resiliency.html is broken, not sure if there is an issue logged already, maybe I should I try fixing it?
I will try fixing it now
Done fixed awaiting merge
I marked it so I hopefully won't forget
@Daenyth I've been out of the loop with the latest
fs2 / cats-effect releases. What would you suggest for the next release of fs2-rabbit? I was waiting for the releases based on cats-2.x.x but I'm not sure if that's ideal. If I do an RC4 with the new dependencies based on Cats 2 are we breaking bincompat with RC3? (this also reminds me that I've never setup MiMa...)
Or it’s sufficient to use default
I haven’t found anything related to providing custom thread pool
I don't know how people are using it tbh. The library doesn't give you a way to provide a custom thread pool (maybe we should now that there's
Blocker et al). It runs on the default EC given by cats-effect. So you could give a custom EC using IO.contextShift(customEC) but I wouldn't worry about it since it's an async client.
I'd use it as is and if it becomes a bottleneck maybe think about giving it a different EC. So far I haven't heard of anyone having issues with it but I haven't used it in a long time so maybe people currently using it can share how they are using it.
i've checked this signature and seems basicPublish is blocking operation
/**
/**
* Publish a message.
*
* Publishing to a non-existent exchange will result in a channel-level
* protocol exception, which closes the channel.
*
* Invocations of <code>Channel#basicPublish</code> will eventually block if a
* <a href="https://www.rabbitmq.com/alarms.html">resource-driven alarm</a> is in effect.
*
* @see com.rabbitmq.client.AMQP.Basic.Publish
* @see <a href="https://www.rabbitmq.com/alarms.html">Resource-driven alarms</a>
* @param exchange the exchange to publish the message to
* @param routingKey the routing key
* @param props other properties for the message - routing headers etc
* @param body the message body
* @throws java.io.IOException if an error is encountered
*/
void basicPublish(String exchange, String routingKey, BasicProperties props, byte[] body) throws IOException;
currently, I'm using the second approach
Blocker just makes clearer that you're shifting the execution into a blocking context
Once that is merged I'll get a PR in for profunktor/fs2-rabbit#230
Thanks to all the contributors :tada: