[bug]: deleting one installed lora resulting in deleting the whole lora folder

[guzmaa]

Is there an existing issue for this problem?

• I have searched the existing issues

Install method

Invoke's Launcher

Operating system

Windows

GPU vendor

Nvidia (CUDA)

GPU model

RTX 5070

GPU VRAM

8GB

Version number

v6.9.0

Browser

No response

System Information

No response

What happened

I downloaded a lora for SDXL model. I installed it early (before it was fully downloaded) which made Invoke not able to recognise the lora installed. I deleted it and scanned for the model again in the folder where I kept all my loras. But it said could ot find directory. That was when I found out the whole folder is gone, not even in the recycle bin. Thus all my installed loras were invalid.

What you expected to happen

I expected only the corrupted installed lora to be deleted, instead the entire folder it was in got deleted

How to reproduce the problem

No response

Additional context

No response

Discord username

No response

[lstein]

I've tried to reproduce this error and I can't seem to. What I did:

1. Created a LoRA directory outside of the INVOKEAI root directory.
2. Populated it with a few good LoRAs
3. Added a truncated LoRA
4. Using the "Scan local directory method," installed and then deleted the truncated LoRA from within the Model Manager - there was no effect on the contents of the LoRA directory.
5. Installed all the good LoRAs as well as the truncated one
6. Deleted the truncated LoRA - no effect
7. Added the truncated and good LoRAs, then deleted all the models one at a time -- no effect on the contents

Please provide a step-by-step recipe for reproducing this error.

Note that InvokeAI should not ever delete models located outside of its root directory. Reciprocally, you should never manually put models into the root directory. The proposed fix from darshjme-codes does not seem to apply to the current InvokeAI source code tree and will not fix the problem.

[github-actions]

There has been no activity in this issue for 30 days. If this issue is still being experienced, please reply with an updated confirmation that the issue is still being experienced with the latest release.

[github-actions]

Due to inactivity, this issue was automatically closed. If you are still experiencing the issue, please recreate the issue.