Versioning / build issues vendoring quack (cutlass/cutedsl pin) for sonic-moe

Open
#718 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
build-system

Research direction

Start by reading the build-time dependency approach in issue #706 and trace how the current cute/cutedsl pin resolves cutlass in the builder. Determine whether sandbox build-time dependencies are required; done means a newer compatible cutlass/cutedsl is available without breaking existing kernels and the pinning strategy is documented in the build configuration.

Written by the indexing model from the issue text.

Description

Context: sonic-moe now hard-requires quack (previously optional alongside its own GEMM backends), so we must vendor it — but that surfaces versioning/build problems.

Problem:

  • Current blocker is on the kernel-builder side: latest quack needs a newer cutlass than what's available.
  • quack → cutedsl → cutlass; the version is pinned in cute, and nixpkgs keeps resolving an older one (~4.5.0).
  • Naive bump is risky since cute/cutedsl frequently change internal APIs.
  • Open question: does the build sandbox need cutedsl/cutlass at build time? (cf. how Helion is handled in #706)

Ask: make a newer cutlass/cutedsl available to the builder without breaking existing kernels, decide a pin/bump strategy, and wire up build-time deps if needed (analogous to the python-depends mechanism from #706).

Cc: @IlyasMoutawwakil

Related to https://github.com/huggingface/kernels/issues/715

Dominant language
Python
Stars
781
Forks
141
Avg merge
1d 10h
Merged PRs (30d)
57

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from huggingface/kernels

All issues in huggingface/kernels

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.