Hal Spitz

Unfortunately, @janko has decided to move on from Shrine. This project was a gift to the community and was a lifesaver for me personally. I can't thank him enough and...

@tomasc I'll pull your PR into my application today/tomorrow. Thanks for the help. hms

@bensheldon I'm start to wonder if it wasn't a misunderstanding on my part. I assumed when the doc's suggested defaults, that I didn't have to set them in my initializer....

Ben, I’ll chase this again in the AMHalOn Jan 30, 2024, at 9:05 PM, bensheldon ***@***.***> wrote: Oh! Maybe you only saw the excerpt that GitHub generated for that code...

@bensheldon I dug in more this morning with fresh eyes. I am unable to reproduce the issue. But just to confirm while I might be crazy, I'm not hallucinating, I...

@bensheldon I did some more digging (when rested) and I'm unable to recreate the problem. I'm leaning toward it was the result of a failing mail job because of a...

@stanhu If you revert the change as you described above, you will find that in the rescue case, any open transitions that are inflight prior to the create_or_find statement, by...

Follow up question: It seems that requesting the worker to self-terminate can leave SolidQueue in a less than correct state. For example, I have seen a record in the Semaphore...

I'm seeing some cleanup issues with the worker being asked to self-terminate. Examples include semaphores that seem to live an abnormally long term. This suggests that my current solution isn't...

@rosa I'm calling terminate via an around perform, so in theory, the worker shouldn't be requesting new work and should be running through it's cleanup protocol. One thing I did...