Please share questions and feedback about the package review process in this thread!
I went through the installation instructions and installed hue. I validated that I can see it with magic list. So far this is great and I am really excited/hopeful.
I am not sure what to do next. For example when I install a rust package I go to crates.io and I can see documentation including examples, links to GitHub and so on. The page that I am looking at does not have any of this information: hue - modular-community
How can I use this hue package in my hello world project? Sorry if this is a silly question and I misread the docs.
Marius
3 Likes
Welcome. This is great feedback. Modular just launched the community package site with assorted backend support. In other words, using magic , github, and prefix.dev, a creator community pipeline now works.
If I hear you correctly, some amount of frontend recommendations or requirements would help the community in using the packages. I agree. This feels to me like the beginning of an organic process that may take a bit.
@Helehex Is hue yours?
@Caroline Thoughts?
1 Like
Yes, echoing Darin’s comment, this is great feedback! And it’s actually something we’re actively working on – essentially, a landing page to highlight projects community distributed via Magic where you can check out the docs for each of the projects. We’re hoping this will land in early 2025.
In the meantime, we do have a basic GitHub pages doc site and we could add the READMEs for all the packages to that site, so that there’s something for folks to reference.
Oh and hue belongs to @Doby!
Ah, no it doesn’t belong to me. Mine is mojmelo
Sorry, I swapped the two names in my head! Yes hue belongs to @miktavarez and mojmelo belongs to @Doby – these are the two community packages you can install so far with Magic 
2 Likes
hey modular community. I am looking to keep a mirror of GitHub - modular/modular-community: A repo to hold community-submitted rattler-build recipes, to make community packages available via the modular-community prefix.dev channel up to date. I’m not sure if HQ wanted some of these branches publicly available.
to replicate run these 1-liner commands in bash after cloning the community repostiory:
git clone https://github.com/modular/modular-community.git
cd modular-community
pixi shell
git remote add upstream https://github.com/modular/modular-community.git
for branch in $(git ls-remote --heads upstream | awk '{print $2}' | sed 's|refs/heads/||'); do git fetch upstream $branch && git checkout -B $branch upstream/$branch && git push -u origin $branch; done
1 Like
i checked again. it checks out on my end. I was looking to deploy pages on my fork
Hi @rcmpge, thanks for flagging – those are intentionally public, just some in-progress work.
Hi! I found what appears to be a race in the post-merge package publishing flow.
PR #334 passed the build matrix on all three platforms and was merged. The subsequent Build and upload packages run built safetensors-mojo successfully on Linux ARM64, but then failed in the compatibility-file commit step with nothing to commit, working tree clean. The upload step was skipped, and the remaining matrix jobs were cancelled.
The commit helper appears to check for changes before git pull, but not afterwards. If another job has already committed the same compatibility-file update, the pull leaves nothing to commit and the otherwise successful publishing run fails.
Could the helper recheck the working tree after pulling and treat the no-op case as success? A harmless compatibility-file race should not prevent successfully built packages from being uploaded.
As a result of this failure, the recipe on main is 0.7.0 while the Prefix channel still provides only 0.5.0. Rerunning the workflow on the current main branch should also recover the missing publication.