Skip to content

Detect invalid model names when migrating 2.3->3.0 #3623

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lstein merged 1 commit into from
Jul 5, 2023
+4 −0
Merged

Detect invalid model names when migrating 2.3->3.0 #3623

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions invokeai/backend/install/migrate_to_3.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -76,6 +76,10 @@ def unique_name(self,name,info)->str:
Create a unique name for a model for use within models.yaml.
'''
done = False

# some model names have slashes in them, which really screws things up
name = name.replace('/','_')

key = ModelManager.create_key(name,info.base_type,info.model_type)
unique_name = key
counter = 1
Expand Down