Fix gemma-3n #3219
Merged
Fix gemma-3n #3219
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
2 participants
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.
the gemma-3n logic in loader.py is no longer being executed after 9c8735a since it will fall into the gemma-3 elif statement. The PR moves gemma-3n inside the gemma-3 logic so that the 3n patch gets applied.
With this change gemma3n vision finetuning works without pinning unsloth and transformers.
Conversational: https://colab.research.google.com/drive/1j-x9oBNu4MUX7bpKjZgozafUDUwgPWGv?usp=sharing
Audio: https://colab.research.google.com/drive/1Roqj8Fb1SA9IOCARBft6l-LZzGiNzdCJ?usp=sharing
Vision: https://colab.research.google.com/drive/1YYBeW1bLsJwK6Ion0DVeMRk2ZuSCTqeU?usp=sharing