How to make savepoints more robust in the face of refactorings ?

Changing the class operators are nested in can break compatibility with existing savepoints. The following piece of code demonstrates this https://gist.github.com/jelmerk/e55abeb0876539975cd32ad0ced8141a If I change Operators in this file to Operators2 i will not be able to recover from a

"Attempt to heart beat failed since the group is rebalancing, try to re-join group" errors

to solve this ? --jelmer

Consuming messages on the same backend

Hi. I have the following problem : we are building a system that will generate any number of different events published to different topics Events have an associated client and a client can express interest in these events. When they do, then for each event we will execute a callback to a remote