fix key convert for lora kohya lora#183
Conversation
Summary of ChangesHello @qzzz95, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request resolves an issue in the key conversion process for LoRA models originating from Kohya, focusing on the text encoder components. The modifications ensure that Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request addresses a bug in the conversion of Kohya's LoRA state dictionaries for the text encoder. The changes correctly parse the layer keys, which use underscores as separators in Kohya's format, and translate them into the dot-separated format expected by the pipeline. The previous implementation was based on an incorrect key format and would fail. This fix is correct and improves compatibility. I have one minor suggestion to improve code conciseness.
6cdb25c to
739e837
Compare
No description provided.