fix: correct cronjob for huey

[ab-smith]

Summary by CodeRabbit

• Chores
  • Enhanced the scheduling of a background process to ensure it starts precisely at 6:00 AM.

[coderabbitai]

Walkthrough

The change updates the cron expression used to schedule the check_controls_with_expired_eta task. The updated decorator now specifies the exact minute ("0") alongside the hour ("6") to ensure the task runs precisely at 6:00 AM daily, rather than sometime during the 6 AM hour.

Changes

File	Change Summary
backend/core/tasks.py	Modified the cron expression in the @db_periodic_task decorator from crontab(hour="6") to crontab(hour="6", minute="0") to specify an exact schedule.

Sequence Diagram(s)

sequenceDiagram
    participant CR as Cron Scheduler
    participant DP as DB Periodic Task Decorator
    participant TC as check_controls_with_expired_eta

    CR->>DP: At 6:00 AM (hour: "6", minute: "0") trigger
    DP->>TC: Invoke scheduled task
    TC-->>DP: Task execution completed

Loading

Poem

I'm a happy rabbit, leaping through the code,
Seeing tasks now run at 6:00 AM mode.
With minute set to zero, precision is the key,
Our scheduler hops along smoothly and free.
Cheers to clear timing, a prance in every byte!
🐇🌅

Tip

🌐 Web search-backed reviews and chat

• We have enabled web search-based reviews and chat for all users. This feature allows CodeRabbit to access the latest documentation and information on the web.
• You can disable this feature by setting web_search: false in the knowledge_base settings.
• Please share any feedback in the Discord discussion.

✨ Finishing Touches

• 📝 Generate Docstrings (Beta)

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

backend/core/tasks.py (1)

20-20: Consider adding a comment to document the schedule.

Add a comment above the decorator to document when this task runs and why, making it easier for other developers to understand the scheduling decision.

+# Run daily at 6:00 AM to check for expired controls and send notifications
 @db_periodic_task(crontab(hour="6", minute="0"))

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d05d330 and 39cc3f0.

📒 Files selected for processing (1)

• backend/core/tasks.py (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (11)

• GitHub Check: startup-functional-test (3.12)
• GitHub Check: startup-docker-compose-test
• GitHub Check: enterprise-startup-functional-test (3.12)
• GitHub Check: enterprise-functional-tests (3.12, chromium)
• GitHub Check: enterprise-startup-docker-compose-test
• GitHub Check: ruff (3.12)
• GitHub Check: functional-tests (3.12, chromium)
• GitHub Check: build (3.12)
• GitHub Check: test (3.12)
• GitHub Check: Analyze (python)
• GitHub Check: Analyze (javascript-typescript)

🔇 Additional comments (1)

backend/core/tasks.py (1)

20-20: LGTM! The cron schedule is now more precise.

The change ensures the task runs exactly at 6:00 AM instead of at a random minute during the 6 AM hour, making the execution time more predictable and easier to monitor.