Filipe Pina

> Hey can you try with v4.0.0-beta? this should be fixed by #1446 @vcastellm not sure if I'm supposed to use any extra flags but 4.0.0-beta3 does not fix my...

Hi @yvanoers, I had not seen that PR no, but (as mentioned in the original description) Jenkins was my motivation indeed. This is actually a PR I've had in my...

ah got it @yvanoers ! I think it would make sense to make it available everywhere though… cron library cares about schedule nothing else. There’s not enough entropy in the...

Thank for taking the time for explaining @yvanoers , I do understand your point much better now. Still I'm not sure how to introduce the hashable parameter without making it...

I was looking into updating my fork 3.2.3 to latest 3.2.7 and couldn't remember why I had a fork, only to go through history and find this feature was the...

> '~' perhaps? @yvanoers thank you for all the feedback. I've also updated `H` to `~` while going through the rest of the review comments. Hope it looks better now!...

Details pushed to https://github.com/fopina/delme/tree/main/dkron_retry_join_does_not_reresolve_dns to make reproducing easier I'd assume with a HA / multi-server setup this won't happen as the server changing IP will retry-join by himself onto the...

after taking a look at `dkron/retry_join.go`, I think the agents are not stuck in a retry loop with an outdated IP, they're not retrying at all. So that is not...

@yvanoers just in case you're still around, would you have any comment on this one? I've tried debugging but I believe part that is handling reconnection (and not re-resolving DNS)...

That's awesome! I did an attempt to trace it but failed... Even when trying with multiple servers as the workaround I mentioned, it still doesn't work. Using the low serf...