Chris Patterson
Chris Patterson
This change is completely moving away from the receive algorithm, which is not going to be accepted. If you could find a less drastic way to achieve the outcome, I'll...
Again, not going to consider it with the whole window change out of the algorithm. Simplify or close.
Does it shut down properly with 8.0.2?
Well, that's strange. Are you waiting for it to exit or just getting hung up on the debugger? There are no issues with any of the tests stopping properly when...
There is a change in the 8.0.4-develop packages that may address this? Did you try it?
Can you post the complete exception with call stack as it was output in the log?
So the consumer keeps on consuming, but you can't publish? What would you expect to happen here? If the exception occurs, the only option is to close the connection, which...
I'm unlikely do anything on this in the next few months, so I'm going to close it.
In this scenario, there are a couple of workarounds available: 1. Don't publish the concrete type, publish the interface instead. In fact, don't create the concrete type at all and...
The challenge with publish topology is that it isn't discoverable. Consumers are easy, the types are well known. However, publishing a message doesn't happen at bus startup (and as I've...