lllyasviel / lllyasviel/stable-diffusion-webui-forge
Lora filename error
- Dominant language
- Python
- Stars
- 13k
- Forks
- 1.7k
- PR merge metrics
- No merged PRs in 30d
Description
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:\SDXLver\IL\stable-diffusion-webui-reForge\modules\extra_networks.py", line 135, in activate
extra_network.activate(p, extra_network_args)
File "E:\SDXLver\IL\stable-diffusion-webui-reForge\extensions-builtin\Lora\extra_networks_lora.py", line 45, in activate
networks.load_networks(names, te_multipliers, unet_multipliers, dyn_dims)
File "E:\SDXLver\IL\stable-diffusion-webui-reForge\extensions-builtin\Lora\networks.py", line 79, in load_networks
errors.display(e, f"loading network {network_on_disk.filename}")
AttributeError: 'NoneType' object has no attribute 'filename'
Havent used this in a while. is there a solution to not recognizing loras if you changed their names manually in the past yet?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with extensions-builtin/Lora/networks.py at load_networks, then follow the call from extensions-builtin/Lora/extra_networks_lora.py:45 and modules/extra_networks.py:135. Reproduce the failure with a LoRA whose filename was changed manually, and determine how the missing network is handled; done means this case no longer raises the reported NoneType filename error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100