Repository navigation
docs: how to keep oMLX's grammar support through a reinstall - #79
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
oMLX is installed with
--with-grammar, and document classification dependson it: without xgrammar the model cannot return structured JSON, so filing
still happens but nothing gets tags, a correspondent or a summary. Nothing
said so anywhere.
Upgrades keep the flag, since Homebrew records the options a formula was built
with. Uninstalling discards that record, so a manual reinstall without the flag
is what loses it. Also covers the two failures that look mysterious: a refused
tap, and a virtualenv broken by a Python upgrade.