Ulf Wiger

I was going to write another explanation for why this functionality was excluded in the first place, but then decided that some of those reasons are invalid, and others are...

If the other process properly handles system messages, there is a way to execute code inside the other process: `sys:replace_state/2` (since OTP R16B). The function is only intended for debugging,...

Note that I haven't reproduced the issue, or added any test case to provoke it. What seems to be happening is that the gproc_dist instance that becomes leader (let's call...

Well, it's a tradeoff. gproc uses at most one monitor per Pid+scope, and this is ensured by `gproc_lib:ensure_monitor/2`, which uses `ets:insert_new/2` - thus very cheap. In order to know when...

PR #89 merged into master and tagged as 0.4

Have you started gproc before trying this? `ets:lookup/2` will not throw a badarg exception just because an object doesn't exist, but does do it e.g. if the table is not...

That's not the intent, no. :) I guess that hasn't been explicitly documented. I'll try to squeeze it into the README.

The erlang docs are correct. I've been meaning to remove that, but it's low priority, since it has no effect either way.

Interesting. One thing to try might be to randomize each timer interval. Jobs doesn't depend on the timers firing exactly, but will calculate for each actual interval how many jobs...

Well, perhaps the simplest way to start would be to write a callback for `check_interval`. https://github.com/uwiger/jobs/blob/master/src/jobs_server.erl#L1745 This would also give an indication of where to try to fix the `jobs_server`...