itv / bucky Goto Github PK

Believed to be innocuous (test needs refactoring), but is breaking fairly frequently on travis.

Assigned to yourself Beni as you said you have an idea of how to fix it.

Thanks

Starting with a blank rabbit container, I:

• publish a message X to an exchange
• start a consumer with a queue that does not exist
• I publish message Y

the consumer will see the message Y, but not X.

How can I configure the (consumer) client so that I can consume both?

With bucky 2.0.0-M7 we seem to have frequent ShutdownSignalException errors in a consumer.

com.rabbitmq.client.ShutdownSignalException: connection error
	at com.rabbitmq.client.impl.AMQConnection.startShutdown(AMQConnection.java:918)
	at com.rabbitmq.client.impl.AMQConnection.shutdown(AMQConnection.java:908)
	at com.rabbitmq.client.impl.AMQConnection.handleFailure(AMQConnection.java:708)
	at com.rabbitmq.client.impl.AMQConnection.access$400(AMQConnection.java:48)
	at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:607)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.io.EOFException: null
	at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:290)
	at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:91)
	at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:164)
	at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:598)

If this is not something trivially reproducible please let me know so I can try to figure out the conditions that lead to this.

Currently bucky attempts to create bindings before the queues are declared causing it to fail.

Stand-alone bindings are not affected:

Both com.itv.bucky.pattern.requeue#requeueDeclarations and registerRequeueConsumerOf define a wait period in case of failure.
In order to avoid confusion only one of the possibilities should be provided.

For instance, for version 1.3.5, bucky-rabbitmq_2.11 is published but bucky-core_2.11 is not.

Bucky recently had support added for FS2 Cats IO, which is great, except that if you're using Http4s then you need version 0.18.x which is currently a milestone version. Even when they release 0.18.0 there are likely to be bugs / issues / unexpected features (as there was in 0.17.0).

Http4s 0.17.x uses FS2 Tasks (FS2 0.9.x) but Bucky current offers no support for that meaning that you can't use Bucky with the latest stable version of Http4s.

Another knock on effect is that it's forcing a Scala-Pact release for the milestone version of 0.18. We will do that release as at least two teams are having problems now, even though I'm not sure it's desirable to release against unstable versions, but it would be nice if the wider world had more choice.

Would it be possible to add FS2 Task support to Bucky please?