Renato Massaro

Hi @firla, @jonathanslenders, I forked `asyncio-redis` and, based on `redis-py-cluster`, I've added support for Redis Cluster using the asyncio lib. It's very hacky but it suits my needs. You can...

This issue will probably result in a server-wide reset (which is totally OK for now). It should be done AFTER #144, which will also require a server-wide reset.

@Deathslayer222 the main problem is this is a "penalty"[1] totally random from the player point of view (every deployment would result in this log message being generated, as well as...

When implementing Bitcoin, make sure to update the tests for: - `VirusHenforcer.valid_payment?/2` - `VirusFlow.start_collect/5` - `VirusCollectRequest.*` (topic test and request test) - `VirusAction.collect/2` (or simply search for #244)

That's a totally valid & fair request. Sorry for not getting back to you earlier. I'm wrapping up a large post where I address all these topics, including how I'll...

Actually this behaviour is quite similar to the one used on `Process.Scheduler` (with the last_checkpoint thing)

Note: the "recursive" in the title is half-right. Except for the recalculation of a process' direct servers (local and remote), all other TOPs recalculation happen asynchronously, using our event-driven architecture....

Note2: It may seem odd that one small change in a process' allocation could lead to hundreds of TOPs being recalculated, but: 1. That's sort of inevitable if we want...

#343 is tangentially related to this issue. We must only emit `TOPRecalcadoEvent` once BOTH the local and remote (if any) servers have gone through the recalque step, otherwise the process...

`recursive` process type was implemented at #410, refer to `LogRecoverProcess` for usage example. Implementation of `recursive` process is based on the `SIGRETARGET` signal. When the process objective is reached, the...