Failed to add arcticdb for both linux and osx on M1 mac.

[freddong]

Checks

• I have checked that this issue has not already been reported.

• I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

pixi init pixi-py --format pyproject
# change pyproject.toml
# from platforms = ["osx-arm64"]
# to platforms = ["linux-64", "osx-arm64"]

pixi add arcticdb

pyproject.toml

[project]
authors = [{name = "XXX", email = "[email protected]"}]
dependencies = []
description = "Add a short description here"
name = "pixi-py"
requires-python = ">= 3.11"
version = "0.1.0"

[build-system]
build-backend = "hatchling.build"
requires = ["hatchling"]

[tool.pixi.project]
channels = ["conda-forge"]
platforms = ["linux-64", "osx-arm64"]

[tool.pixi.pypi-dependencies]
pixi_py = { path = ".", editable = true }

[tool.pixi.tasks]

[tool.pixi.dependencies]
arcticdb = ">=4.5.0,<5"

Issue description

pixi 0.30.0, installed with brew.

on M1 mac:
It's OK to install for osx only.

pixi init pixi-py --format pyproject
pixi add arcticdb

The output is Added arcticdb >=4.5.0,<5.

But it failed to add for linux and osx.

pixi init pixi-py --format pyproject
# change pyproject.toml
# from platforms = ["osx-arm64"]
# to platforms = ["linux-64", "osx-arm64"]

pixi add arcticdb

the outpus is:
~/pixi-py $ pixi add arcticdb
⠤ updating lock-file [00:00:00] [━━━━━━━━━━━━━━━━━━━━━━━─────────────────] 4/7
⠂ default:linux-64 [00:00:00] loading repodata thread 'tokio-runtime-worker' panicked at library/core/src/slice/sort/shared/smallsort.rs:862:5:
user-provided comparison function does not correctly implement a total order
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

It crashed.

Expected behavior

Successful installation for linux and osx.

[ruben-arts]

This is because of the brew installation, the compile with the latest rust seems to have broken something in the binary. We're not yet building with rust 1.81 so the issue is not fixed.

Related: #2122

[ruben-arts]

I'm confident this is fixed in v0.32.1, so I'm closing it. Please reopen if this was not the case