Skip to content

🔄 Auto-Sync: ml-explore/mlx-swift main (5f117a2, 2 commit(s)) - #31

Merged
solderzzc merged 3 commits into
mainfrom
bot/upstream-5f117a2-de0b43c
Oct 31, 2026
Merged

solderzzc merged 3 commits into
mainfrom
bot/upstream-5f117a2-de0b43c

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

Automated real merge of ml-explore/mlx-swift main (5f117a2, 2 commit(s) not yet in this fork) into main. Upstream changes: ml-explore/mlx-swift@78d3cc1...5f117a2

Merge this PR with a merge commit ("Create a merge commit"), not squash or rebase. Squashing orphans the upstream commits and the fork commits that downstream repos pin (submodule SHAs).

Upstream commits

  • 5f117a2 fix callers of mlx_vector_array_values to handle potentially empty results (#518) (David Koski)
  • 075f458 switch some tests to Swift Testing (#519) (David Koski)

Needs a human look

  • Nothing flagged.

What was checked

  • Git merged cleanly (no conflicts, no -X ours/theirs); the fork's workflows were restored unchanged.
  • Size: 39 files changed, 1750 insertions(+), 1515 deletions(-).
  • Syntax: 39 changed Swift file(s) parsed with swiftc 6.2.
  • Not run by the bot: a build, the tests, a Metal toolchain. CI on this PR must be green before merging.

Bot disclosure

Prepared by the upstream-sync GitHub Actions workflow. The workflow never approves, reviews or merges; no human has reviewed this merge yet.

  • I have read this PR description in full and approve it as my own

davidkoski and others added 3 commits October 30, 2026 15:24
* switch some tests to Swift Testing

- migrate off of xctest onto swift testing
- this is round 1
…sults (ml-explore#518)

* fix callers of mlx_vector_array_values to handle potentially empty results

- if a call to mlx_quantize fails it can produce an empty result
- but the calling code expects 2 or more valeus in the array
- if using withError to catch the error, this crashes instead

- fix by allowing callers to specify the minimum number of arrays they need
- those values are not usable, but work fine as stand-ins

- fixes ml-explore#516
Automated merge by the upstream-sync workflow. 2 upstream commit(s). Merge with a merge commit, not squash/rebase.
@solderzzc
solderzzc merged commit 5d78578 into main Oct 31, 2026
8 checks passed
@solderzzc
solderzzc deleted the bot/upstream-5f117a2-de0b43c branch October 31, 2026 19:02
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.

2 participants