fix(apalis-redis): enable "allow-undeclared-keys" for dragonflydb in stats.lua
#567
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#506 introduced a bug when using
apalis-redis
with dragonfly DB: Since keys get programatically generated, in the for loop counting running jobs, the script does not work with dragonfly, which forbids using undeclared keys by default: https://www.dragonflydb.io/docs/managing-dragonfly/scripting#allowing-undeclared-keys .With Redis, accessing undeclared keys is allowed, but considered a bad practice: https://redis.io/docs/latest/commands/eval/#:~:text=Important%3A%20to,in%20the%20database
A long-term fix would probably be something like storing a counter of running jobs somewhere, and pass the key of the counter to the script