Skip to content

[HOTFIX] Dont schedule tasks if already queued#2885

Merged
gantoine merged 2 commits intomasterfrom
hotfix-multi-task-schedule
Jan 10, 2026
Merged

[HOTFIX] Dont schedule tasks if already queued#2885
gantoine merged 2 commits intomasterfrom
hotfix-multi-task-schedule

Conversation

@gantoine
Copy link
Copy Markdown
Member

@gantoine gantoine commented Jan 9, 2026

Description
Explain the changes or enhancements you are proposing with this pull request.

Checklist
Please check all that apply.

  • I've tested the changes locally
  • I've updated relevant comments
  • I've assigned reviewers for this PR
  • I've added unit tests that cover the changes

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @gantoine, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This hotfix addresses an issue where tasks could be redundantly scheduled even if they were already present in a processing queue. The primary goal is to ensure task uniqueness by extending the check for existing jobs to include both the main task scheduler and the low-priority queue, thereby preventing unnecessary re-scheduling and potential resource waste. A new unit test has been added to validate this behavior.

Highlights

  • Task Scheduling Logic Update: Modified the _get_existing_job method to check for existing tasks in both the main task scheduler (tasks_scheduler) and the low-priority queue (low_prio_queue) to prevent duplicate scheduling.
  • New Unit Test for Task Requeue Prevention: Added a new test file (backend/tests/tasks/test_prevent_requeue.py) with a dedicated test case to verify that tasks are not re-scheduled if they are already present in either queue.
  • Metadata Handler Test Updates: Introduced imports for FlashpointHandler, HLTBHandler, and TGDBHandler in backend/tests/tasks/test_scan_library.py and included them in the mocked is_enabled checks for the ScanLibraryTask test.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a hotfix to prevent tasks from being scheduled if they are already present in the low_prio_queue. The core logic change in tasks.py is sound and is accompanied by a well-written unit test in test_prevent_requeue.py. My main feedback includes a suggestion for a minor performance improvement in tasks.py. Additionally, I've noticed that the changes in test_scan_library.py seem unrelated to the hotfix's purpose and should ideally be submitted in a separate pull request to maintain a clean and focused commit history.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Jan 9, 2026

Test Results

703 tests  +1   702 ✅ +1   1m 23s ⏱️ -3s
  1 suites ±0     1 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit 743bddc. ± Comparison against base commit 9fe49ba.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Copy Markdown
Contributor

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines Covered Coverage Threshold Status
12121 7886 65% 0% 🟢

New Files

No new covered files...

Modified Files

File Coverage Status
backend/tasks/tasks.py 96% 🟢
TOTAL 96% 🟢

updated for commit: 743bddc by action🐍

@gantoine
Copy link
Copy Markdown
Member Author

/gemini review

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a hotfix to prevent scheduling tasks that are already present in the queue. The core logic change in tasks.py correctly checks both the scheduler and the queue for existing jobs, which effectively solves the issue. It's great to see that a new test file has been added to verify this behavior. I've provided a couple of suggestions in the tests to enhance maintainability, but overall, this is a well-executed fix.

@gantoine gantoine merged commit 3d7a9c2 into master Jan 10, 2026
8 checks passed
@gantoine gantoine deleted the hotfix-multi-task-schedule branch January 10, 2026 14:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant