Wanderson Pinto dos Santos 0e03542db5 fix: single task executor getting all tasks from Redis queue (#7330) ...

### What problem does this PR solve?

Currently, as long as there are tasks in Redis, this loop will keep
getting the tasks. This will lead to a single task executor with many
tasks in the pending state. Then we need to wait for the pending tasks
to get them back in the queue.

In first place, if we set the `MAX_CONCURRENT_TASKS` to X, then only X
tasks should be picked from the queue, and others should be left in the
queue for other `task_executors` or be picked after 1 of the spots in
the current executor gets free. This PR ensures this behavior.

The additional changes were due to the Ruff linting in pre-commit. But I
believe these are expected to keep the coding style.

### Type of change

- [X] Bug Fix (non-breaking change which fixes an issue)
- [ ] New Feature (non-breaking change which adds functionality)
- [ ] Documentation Update
- [ ] Refactoring
- [ ] Performance Improvement
- [ ] Other (please describe):

Co-authored-by: Zhichang Yu <yuzhichang@gmail.com>

2025-06-06 14:32:35 +08:00

..

cache_file_svr.py

Format: dos2unix (#4467)

2025-01-13 18:19:01 +08:00

discord_svr.py

Use consistent log file names, introduced initLogger (#3403)

2024-11-14 17:13:48 +08:00

jina_server.py

Update comments (#4569)

2025-01-21 20:52:28 +08:00

task_executor.py

fix: single task executor getting all tasks from Redis queue (#7330)

2025-06-06 14:32:35 +08:00