Redis atomic job queue

[kaplanelad]

No description provided.

[kaplanelad]

Hey @DenuxPlays and @jtwaleson,

Following up on our discussion in #1462 and the related PR: #1384 — I've fixed the positional issue in the Redis queue implementation.

Please test this branch with a Loco app and help verify the full Redis queue flow.

Specifically, please check:

• End-to-end queue behavior in your app
• Enqueueing, processing, and retry logic
• Any edge cases or unusual behavior
• Any other scenarios you think are worth testing

If you find any issues, feel free to either push a fix directly to my PR or comment here with a description and (if possible) steps to reproduce it

Thanks!

[DenuxPlays]

Hey,

Haven't noticed anything but I am not done testing

Just wanted to say that we should probably Release an RC asking more to Test their application to cover Some edge cases we probably don't think about

[kaplanelad]

Thanks, @DenuxPlays! Looking forward to your response once you're done testing.

[DenuxPlays]

Hey,

sorry for the delay but I've tested it.

I hadn't had any issues with atomcity so this approach should work in production (I would still release an rc to widen our test cases).
I've noticed an increased redis CPU usage compared to the old implementation but nothing drastically. It was so minimal but it may also be just some test fluctuations. (less then 0.2% but consistent)