feat(llamacpp): support .zip archives for manual backend install

[github-roushan]

Describe Your Changes

• UI: allows one to upload .zip backends in “Install Backend from File”
• Tauri: add .zip extraction to decompress; add zip crate
• Extension: accept .zip in installBackend; tolerate .zip/.tar.gz asset names
• Keep remote downloads on .tar.gz to match release assets

Fixes Issues

• Closes feat: Allow to install backend from file with .zip instead of .tar.gz #6519

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Add support for .zip archives in llamacpp backend installation, updating UI and backend logic, and adding necessary dependencies.

• UI:
  • Allow .zip backend uploads in "Install Backend from File" in $providerName.tsx.
• Backend:
  • Update installBackend in index.ts to accept .zip files.
  • Modify decompress() in commands.rs to handle .zip extraction.
• Dependencies:
  • Add zip crate to Cargo.toml and Cargo.lock for .zip support.
• Misc:
  • Keep remote downloads as .tar.gz to match release assets.
• Fixes:
  • Closes feat: Allow to install backend from file with .zip instead of .tar.gz #6519.

^{This description was created by for 500fbd8. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 500fbd8 in 1 minute and 13 seconds. Click for details.

• Reviewed 377 lines of code in 6 files
• Skipped 1 files when reviewing.
• Skipped posting 6 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. src-tauri/Cargo.toml:61

• Draft comment:
  Ensure that the dependency 'zip = "0.6"' meets the feature requirements used in the decompress command. Consider verifying compatibility with your extraction logic.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. src-tauri/src/core/filesystem/commands.rs:199

• Draft comment:
  The file extension check uses a case-sensitive ends_with. Consider normalizing the string (e.g. to lowercase) or using a more robust method (like Path::extension) to handle cases like '.ZIP' or mixed case.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

3. web-app/src/routes/settings/providers/$providerName.tsx:391

• Draft comment:
  The inline comment states to replace spaces with dashes and convert to lowercase, but the code only replaces spaces. If lowercase conversion is desired, chain a toLowerCase() call for consistency.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

4. web-app/src/routes/settings/providers/$providerName.tsx:787

• Draft comment:
  When mapping over provider models, the key is set to the index. It's more stable to use a unique identifier like model.id if available.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

5. src-tauri/src/core/filesystem/commands.rs:10

• Draft comment:
  Multiple command functions take a Vec as arguments. Consider defining a dedicated parameter struct for better type safety and clearer intent.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

6. src-tauri/src/core/filesystem/commands.rs:131

• Draft comment:
  There's a TODO comment about implementing proper scope checks in write_yaml. Consider adding a tracking issue or reminder to implement robust security checks when the FS API is removed from the frontend.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_35jc7Bsmg2AIezSJ

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[Minh141120]

Hi @github-roushan, Thanks for making the contribution. We'll review it and let you know when it's ready

[qnixsynapse]

Please remove all the lock file changes.

[github-roushan]

Please remove all the lock file changes.

lock files are pinning exact versions of transitive dependencies. Without them, two people doing yarn install at different times might get different dependency trees, and the app could behave differently or even break.

[github-roushan]

Please remove all the lock file changes.

@qnixsynapse . would you please review this again. I see lock files in both cargo and extensions have been pushed before. Infact removing the lock files are breaking the build. I believe lock file is needed as i added a new create zip and its actual version needs to be reflected. Even louis has pushed a PR with lock files around 5 days ago.

[qnixsynapse]

Because of security issues, I don't really recommend adding lock file changes. Team member can do this because they monitor what's happening.

Rest LGTM.

[github-roushan]

can you merge this though @qnixsynapse

[qnixsynapse]

You need to rebase and remove Cargo.lock file. That diff is huge.

[github-roushan]

You need to rebase and remove Cargo.lock file. That diff is huge.

Hey @qnixsynapse . I have rebased to the latest dev commit as of this comment. Also I have tested with removing .lock files. From my google search i understand that .lock files shouldn't be removed (or the build is failing, you can try, yourself) when you have added a new crate (zip 0.6) for zip functionality. as these needs to finds the right dependencies for the version of zip crate that was installed. Please go through actual Cargo.toml to see the changes that was done.