Closed cearny closed 1 year ago
Thanks for reporting this, @cearny! I've just released the fix, please see https://github.com/HangfireIO/Hangfire.InMemory/releases/tag/v0.5.1. There was a problem with struct implementation that caused values in sets to be not updatable.
Actually, thank you! And this fix was also educative for me as I haven't gotten around to using readonly struct
s yet 😁
I'll give the new package version a try later today, but from just looking at the diff, I think that solves the issue.
Yeah, immutable structs are like a mantra, and always should be used together 🥸.
No need to test it today – you did your job, I did my job, so let's celebrate 🍾🥳.
Hi, after updating to version 0.5.0, it seems that after running a recurring job the first time and about when hitting the second execution scheduled time, somehow it always is marked as being "updated", and so I am getting this log output (set to Trace):
The CPU spikes a lot and it seems the app ends up in an infinite loop. Downgrading to 0.4.1 fixes this.
This is the job definition (ASP.NET Core app):
I have checked and the job does not throw; as I mentioned, downgrading fixes this.
Let me know if you need more details.