Skip to content

Fix background updater - #54

Merged
AnthonyRonning merged 1 commit into
masterfrom
background-downloader
Apr 12, 2025
Merged

AnthonyRonning merged 1 commit into
masterfrom
background-downloader

Conversation

@AnthonyRonning

@AnthonyRonning AnthonyRonning commented Apr 12, 2025 •

Copy link
Copy Markdown
Contributor

Summary by CodeRabbit

  • New Features
    • Improved update management now prevents redundant update downloads and notifications, ensuring a smoother and less disruptive update experience for users.

@coderabbitai

coderabbitai Bot commented Apr 12, 2025 •

Copy link
Copy Markdown

Walkthrough

The changes consist of two parts. First, a new dependency once_cell = "1.18.0" is added to the project's Cargo.toml file. Second, modifications in the library source include introducing two global static variables—one to track if an update has been downloaded and another to store the current version—to prevent redundant update downloads and notifications. Minor formatting adjustments were also applied.

Changes

File(s) Change Summary
frontend/src-tauri/Cargo.toml Added new dependency once_cell = "1.18.0" under the [dependencies] section.
frontend/src-tauri/src/lib.rs Introduced global variables (UPDATE_DOWNLOADED as AtomicBool and CURRENT_VERSION as Lazy<Mutex<String>>) and modified check_for_updates to prevent redundant update downloads and notifications; applied minor formatting changes.

Sequence Diagram(s)

sequenceDiagram
    participant App as Tauri App
    participant Checker as Update Checker (lib.rs)
    participant State as Global State

    App->>Checker: Invoke check_for_updates()
    Checker->>State: Read CURRENT_VERSION & UPDATE_DOWNLOADED
    alt Update already downloaded?
        Checker-->>App: Log "Update already downloaded" and exit
    else
        Checker->>Checker: Compare CURRENT_VERSION with available update version
        Checker->>State: Update CURRENT_VERSION and set UPDATE_DOWNLOADED to true
        Checker-->>App: Proceed with update installation/notification
    end
Loading

Poem

I'm a rabbit with a curious cheer,
Skipping through code, the updates are here!
A new dependency hops into view,
With globals set to keep things true.
No more duplicate hops in the night,
Carrots and code make it just right!
🥕🐇 Happy coding, day and night!

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)
  • We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.
✨ Finishing Touches
  • 📝 Generate Docstrings

🪧 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.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @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.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying maple with  Cloudflare Pages  Cloudflare Pages

Latest commit: f57e1cc
Status: ✅  Deploy successful!
Preview URL: https://ef7adfd1.maple-ca8.pages.dev
Branch Preview URL: https://background-downloader.maple-ca8.pages.dev

View logs

@greptile-apps greptile-apps Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

PR Summary

This PR enhances the application's update mechanism by preventing redundant downloads and notifications for the same version updates.

  • Added once_cell dependency (v1.18.0) in frontend/src-tauri/Cargo.toml for thread-safe lazy initialization
  • Implemented global state tracking with UPDATE_DOWNLOADED (AtomicBool) and CURRENT_VERSION (Mutex) in frontend/src-tauri/src/lib.rs
  • Added version comparison logic to skip re-downloading already downloaded updates
  • Improved update dialog with more descriptive title "Maple Update" and clearer user messaging
  • Implemented proper mutex locking with error handling for thread-safe version tracking

Greptile AI

2 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

Comment thread frontend/src-tauri/src/lib.rs

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
frontend/src-tauri/src/lib.rs (1)

230-248: Effective early return logic prevents redundant downloads.

The implementation correctly checks if the specific version has already been downloaded before proceeding with the download process. This prevents unnecessary network traffic and improves the user experience by avoiding duplicate downloads of the same update.

One minor suggestion: consider adding a debug log at the beginning of this function to record the update version being checked against the current version for easier troubleshooting.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between dcd4ee2 and f57e1cc.

⛔ Files ignored due to path filters (1)
  • frontend/src-tauri/Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (2)
  • frontend/src-tauri/Cargo.toml (1 hunks)
  • frontend/src-tauri/src/lib.rs (5 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build-macos (universal-apple-darwin)
  • GitHub Check: build-linux
  • GitHub Check: Cloudflare Pages
🔇 Additional comments (6)
frontend/src-tauri/Cargo.toml (1)

32-32: Appropriate dependency addition for global state management.

The addition of once_cell = "1.18.0" is appropriate for implementing thread-safe lazy initialization of static variables, which will be used to prevent redundant update downloads and notifications.

frontend/src-tauri/src/lib.rs (5)

198-209: Good implementation of global state for update tracking.

The introduction of global static variables using once_cell and atomic types provides a thread-safe mechanism to track update status across multiple update check operations. The AtomicBool and Mutex wrappers ensure thread safety when accessing these shared state variables from different async tasks.


275-293: Good state management after successful update installation.

The code properly updates the global state after a successful update installation, storing the version information and preventing redundant notifications for the same update. This ensures users aren't repeatedly prompted about the same update.


56-56: Clean code formatting improvement.

Removal of unnecessary blank lines improves code readability.

Also applies to: 62-62, 67-67


309-309: Clear and concise dialog title.

The dialog title change to "Maple Update" provides better context to the user about the nature of the notification.


56-70: Verify update check behavior with hourly interval.

The hourly update check mechanism will continue to run as before, but now with the added benefit of skipping redundant downloads. However, it might be worth considering whether updates should be re-checked after the application has been running for a while, even if an update was previously downloaded but not installed.

Consider if this edge case needs handling: if a user ignores an update notification and keeps the application running for days, should the application eventually re-prompt them about the pending update?

@AnthonyRonning
AnthonyRonning merged commit f5065ce into master Apr 12, 2025
@AnthonyRonning
AnthonyRonning deleted the background-downloader branch April 12, 2025 16:41
benthecarman pushed a commit to benthecarman/Maple that referenced this pull request Aug 26, 2026
…go-audit-maple-proxy

Security: enforce daily RustSec advisory checks
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