Skip to content

fix: mlx backend fails to compile; publish containers to correct ghcr org - #13

Merged
bong-water-water-bong merged 2 commits into
mainfrom
fix/mlx-build-and-ghcr
Aug 9, 2026
Merged

bong-water-water-bong merged 2 commits into
mainfrom
fix/mlx-build-and-ghcr

Conversation

@bong-water-water-bong

Copy link
Copy Markdown
Owner

Two CI fixes:

  1. Validate New llama.cpp Release (Windows build) has been broken since the mlx backend landed — mlx-engine|mlx is in LEMON_BACKENDS unconditionally, but mlx_server.cpp referenced an undefined SPEC, closed namespace backends before the anonymous/mlx namespaces (putting them at lemon:: scope, mismatching the header's lemon::backends::mlx), and never included mlx.h for its descriptor. Verified with a local g++ syntax check.
  2. Publish Containers pushes to ghcr.io/lemonade-sdk/lemonade/build-environment, which the repo's GITHUB_TOKEN can't write (permission_denied: The requested installation does not exist — failing daily since Aug 6). Now uses ghcr.io/${{ github.repository }}.

… org

mlx_server.cpp: replace undefined SPEC with mlx::spec(), keep the
anonymous namespace and mlx namespace inside lemon::backends (the early
} // namespace backends put them at lemon:: scope), and include mlx.h
for the descriptor. The mlx backend is in LEMON_BACKENDS unconditionally,
so every Windows build has been broken since the backend was added -
first surfaced by the Validate New llama.cpp Release run.

build-container.yml: push to ghcr.io/${{ github.repository }} instead of
the stale ghcr.io/lemonade-sdk org, which denies the repo's GITHUB_TOKEN
(permission_denied: The requested installation does not exist).
@bong-water-water-bong
bong-water-water-bong merged commit da7c355 into main Aug 9, 2026
46 of 78 checks passed
@bong-water-water-bong
bong-water-water-bong deleted the fix/mlx-build-and-ghcr branch August 9, 2026 21:58
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.

1 participant