fix lora settings: item filename keyerror

[light-and-ray]

Description

Sometimes opening settings doesn't work due to this error:

stable-diffusion-webui/modules/ui_extra_networks_user_metadata.py", line 77, in get_card_html
    filename, _ = os.path.splitext(item["filename"])
KeyError: filename

It happens because lora's name is alias

Checklist:

• I have read contributing wiki page
• I have performed a self-review of my own code
• My code follows the style guidelines
• My code passes tests

[w-e-w]

It happens because lora's name is alias

in what case does that happen?

[light-and-ray]

After editing cards with different names and aliases. If I understand correctly. Or just after opening and closing. It's also connected with preview update, the error happens there

In general I had very inconsistent card settings, and after adding these 2 lines all started to be ok. I found this solution while making sdxl support in my old-sd-firstpasser extension, because SD model field is filled in the same place

[w-e-w]

no that is not the fix

thes line of code is just a thread safe check to make sure that the entry is already loaded
otherwise it stopped processing

this functuon is for creading cards not selecting lora in prompt
name MUST be unique and and in available_networks
available_network_aliases should not be used as a fallback

if you use available_network_aliases as fallback then you could end up in a situation where the lora list is not fully loaded but a but the matching alias is, which would then cause you to select the wrong lora to be edited

the issue as you have written is for some reason

    filename, _ = os.path.splitext(item["filename"])
KeyError: filename

so the investigation subsequent fix fix should be about why the filename key is missing
and not adding a problematic pullback

[light-and-ray]

I don't understand

this functuon is for creading cards not selecting lora in prompt

I know, and I write in the description about cards in ui

if you use available_network_aliases as fallback then you could end up in a situation where the lora list is not fully loaded but a but the matching alias is, which would then cause you to select the wrong lora to be edited

Available networks are loaded first, and then "info" objects for cards are being loaded. How does it possible to not have lora list fully loaded

so the investigation subsequent fix fix should be about why the filename key is missing
and not adding a problematic pullback

Okay I'll find a way to reproduce

[light-and-ray]

Oh I see, thank you @w-e-w . This problem happens only if the backend was reloaded, but the frontend - not. Users need to press reload button