feat(queue): support getCountsPerPriority method [elixir] [dotnet]

[roggervalf]

Port Impact Checklist

• Python – does this change need to be ported or documented in the Python library?
• Elixir – does this change need to be ported or documented in the Elixir library?
• PHP – does this change need to be ported or documented in the PHP library?
• Rust – does this change need to be ported or documented in the Rust library?
• .NET – does this change need to be ported or documented in the .NET library?

Why

Enter your explanation here.

How

Enter the implementation details here.

Additional Notes (Optional)

Any extra info here.

[Copilot]

Pull request overview

Adds Elixir support for getCountsPerPriority by introducing a new get_counts_per_priority/3 API and backing Redis script call, while also aligning multiple ports to the 2-key getCountsPerPriority-2.lua signature (wait + prioritized).

Changes:

• Add Elixir Queue.get_counts_per_priority/3 + backend plumbing and tests.
• Update getCountsPerPriority-2.lua (and callers across Node/Rust/Python/PHP) to pass only the required keys.
• Update Rust/Python/PHP script registries/wrappers to reference the -2.lua script variant.

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/commands/getCountsPerPriority-2.lua	Adjust Lua script key contract to (wait, prioritized).
src/classes/redis-queue-backend.ts	Update Node Redis backend args to pass only required keys.
rust/src/scripts.rs	Register getCountsPerPriority as a 2-key script using getCountsPerPriority-2.lua.
rust/src/queue.rs	Pass only wait + prioritized keys when invoking the script.
python/bullmq/scripts.py	Build script args with only wait + prioritized keys.
python/bullmq/redis_connection.py	Update script filename mapping to getCountsPerPriority-2.lua.
php/src/Scripts.php	Pass only wait + prioritized keys and exec getCountsPerPriority-2.lua.
elixir/test/bullmq/queue_getters_test.exs	Add coverage for get_counts_per_priority/3, including paused behavior and deduping.
elixir/lib/bullmq/scripts.ex	Add Redis script wrapper get_counts_per_priority/3.
elixir/lib/bullmq/queue.ex	Add public API get_counts_per_priority/3 and GenServer handler.
elixir/lib/bullmq/backends/redis.ex	Implement backend callback for Redis backend.
elixir/lib/bullmq/backend.ex	Add backend callback + dispatcher function for counts-per-priority.

Suppressed comments (2)

src/commands/getCountsPerPriority-2.lua:13

• This script now treats KEYS[2] as the prioritized ZSET. Callers that still pass the legacy 4-key list (wait, paused, meta, prioritized) will end up with KEYS[2]=paused, and ZCOUNT will hit a list key (WRONGTYPE) or count the wrong structure. For example, the .NET RedisBackend still passes 4 keys. Consider making the script backward compatible by preferring KEYS[4] when present.
  src/commands/getCountsPerPriority-2.lua:6
• The top-of-file comment still says "Get counts per provided states", but this script counts per priority values. Updating this header avoids misleading documentation for maintainers.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[roggervalf]

on other ports, logic of script doesn't change only removing extra pause key

[manast]

yes, but was this functionality actually working on all the ports?

[roggervalf]

wrong keys being provided

[roggervalf]

missing to emit event

[roggervalf]

we do not save short version of priority in node

[manast]

This must have been broken in all ports as it is using an invalid key, are we lacking tests to cover for this functionality?

[roggervalf]

I reviewed all ports:

• dotnet: added missing test cases and missed getCountsPerPriority method
• php: it´s covered by test cases in pause and getCountsPerPriority
• python: same as above
• rust: same as above