mx fails with "no primary suite found"
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 205
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
All mx commands fail on my system with:
"no primary suite found for < command name >"
I'm on Windows with the latest release, but I've confirmed it happens on Ubuntu as well.
Bigger problem: there is no documentation anywhere on what a suite is. There is some mention of suites here: https://github.com/graalvm/mx, but it's not enough. Not sure how to fix the problem.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with an mx command on Windows or Ubuntu using the latest release. Read the existing suite references in the mx repository and trace how command execution resolves its primary suite. Done means the failure is addressed and documentation explains what a suite is and how users can configure or select one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100