lmstudio: 0.3.3 -> 0.3.4

[crertel]

Changes

Full Changelog

Summary

What’s new in 0.3.4:

New

• MLX support
• MLX KV caching
• Mission Control: Cmd+Shift+M to search for models, Cmd+Shift+R to manage LM Runtimes
• Set Structured Output (JSON Schema) from the UI

Bug Fixes

• Fix for Black Screen after prolonged use (reference: lmstudio-bug-tracker#98)
• Fix for no port other than 1234 working for the local server (reference: lms#80)
• Fix for embedding API not working from Obsidian (reference: tracker#142)
• Fix for RAG sometimes failing during document processing

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[eeedean]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 347599

---

aarch64-darwin

❌ 1 package failed to build:

• lmstudio

x86_64-linux

✅ 1 package built:

• lmstudio

---

Did they change the URL for aarch64-darwin?
it seems to be now:

https://releases.lmstudio.ai/darwin/arm64/0.3.4/3/LM-Studio-0.3.4-arm64.dmg

instead of

https://releases.lmstudio.ai/darwin/arm64/0.3.4/LM-Studio-0.3.4-arm64.dmg

They finally added the build revision into the URL for aarch64-darwin, too. Did you test it beforehand? I suspect, it did not ever work with the current URL in the PR.

[eeedean]

• url needs change including build revision:

https://releases.lmstudio.ai/darwin/arm64/${version}/3/LM-Studio-${version}-arm64.dmg

maybe, we even want to put the build revision into its own variable, as it is present in both URLs now?
https://releases.lmstudio.ai/darwin/arm64/${version}/${build-revision}/LM-Studio-${version}-arm64.dmg

[crertel]

Perhaps--but the thing is, they keep changing around the URLs on us (at least for the Linux folks--Mac seems stabler). I'm kinda wondering if we should go the other way and just hardcode the URL every time until they get their act together.

[crertel]

@eeedean thanks for catching that bad URL, must've fat-fingered it. Not on Mac so my testing there isn't super thorough.

[eeedean]

nixpkgs-review result

Generated using nixpkgs-review.

Command: nixpkgs-review pr 347599

---

aarch64-darwin

✅ 1 package built:

• lmstudio

x86_64-linux

✅ 1 package built:

• lmstudio

• I would appreciate a squash of the commits, please. Then it's perfect imo. 🐱

Edit: Also sorry for taking so long to get back to you ☹️

[crertel]

@eeedean done!

[eeedean]

In case, you don’t know this friend, yet: https://github.com/nixos/nixpkgs-merge-bot#features

[crertel]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-merge-bot]

@crertel merge not permitted (#305350):
pr author is not in restricted authors list, in the list are: r-ryantm

[eeedean]

I could swear, I already used this bad boy to merge one of my PRs… I‘ll investigate again 😅

[eeedean]

@crertel , merge bot seems to be an in-progress-RFC and not sharp yep. Currently, it does only mention the merge queue issue, as seen. That does at least motivate some commiter (in this case Lassalus, who also is involved in creation of the bot and RFC — Thanks!!) to press the holy button.

See for more information here.

Anyway: seems reasonable to let the bot put an approved PR into the merge queue. Works as designed!