InvokeAI
InvokeAI copied to clipboard
[bug]: Models not getting detected while there are jpg and json files in the same folder
Is there an existing issue for this problem?
- [X] I have searched the existing issues
Operating system
Windows
GPU vendor
Nvidia (CUDA)
GPU model
4090
GPU VRAM
24GB
Version number
3.7.0
Browser
123.0
Python dependencies
No response
What happened
Syncing/scanning the models through the Invoke webUI seems to skip over the checkpoint files when there are jpg and json files in the same folder.
What you expected to happen
I expected the models to get detected after syncing.
How to reproduce the problem
Place jpg and json files (for metadata/checkpoint browsing) in the same folder the models are in and try syncing models. Might need to pass a specific file size / file count threshold to reproduce it (see Additional context).
Additional context
I haven't tested whether there is a file size / file count threshold for this happening but it's possible that my relatively large collection of checkpoints (265GB / 230 files total including the jpg/json files) is causing this.
The 'Please select the scheduler prediction type of the checkpoint' won't even appear in the console while the jpg/json files are there in the folder, it just skips over the models completely without any errors as if they were not there.
Deleting the jpg/json files makes it function normally again.
Discord username
nez.0
Sorry for the late response. We've been hard at work on a new model manager for the upcoming v4 release. I tried putting JPG and JSON files in the models dir and this doesn't cause any problems.
I'm going to say the solution here is to upgrade to v4 when it is released (we are on RC5 now). We won't be making bug fixes for v3.
If the issue still exists on v4, please @ me on this issue and provide some example files and folder structure so we can reproduce the issue.
Discord conversation: https://discord.com/channels/1020123559063990373/1020123559831539744/1231339165220733000
@nezdot Please provide some detail on how to reproduce this issue