KeyError: 'quicksettings'

Question

KeyError: 'quicksettings'

sleel opened this issue a year ago · comments

repo_type:AUTOMATIC1111

KeyError Traceback (most recent call last)
in <cell line: 115>()
113 config["show_progress_every_n_steps"] = 10
114 config["show_progressbar"] = True
--> 115 if config["quicksettings"]:
116 config["quicksettings"] = "sd_model_checkpoint, sd_vae, CLIP_stop_at_last_layers, use_old_karras_scheduler_sigmas, always_discard_next_to_last_sigma"
117 else:

KeyError: 'quicksettings'

repo_type:Anapnoe no such problem

Ryuzhal commented a year ago

same here

Furqanil Taqwa · Answer 1 · Tue May 16 2023 21:38:24 GMT+0800 (China Standard Time)

It should have been fixed with this commit: 8a13dce. Please try it and let me know if there is something wrong.

Thank you.

ReEnMikki · Answer 2 · Wed May 17 2023 00:56:37 GMT+0800 (China Standard Time)

It should have been fixed with this commit: 8a13dce. Please try it and let me know if there is something wrong.

Thank you.

It still doesn't fix the error

Furqanil Taqwa · Answer 3 · Wed May 17 2023 07:12:47 GMT+0800 (China Standard Time)

It should have been fixed with this commit: 8a13dce. Please try it and let me know if there is something wrong.
Thank you.

It still doesn't fix the error

Can you confirm it still hasnt fixed? because there is no error in my side, thank you

Furqanil Taqwa · Answer 4 · Wed May 17 2023 07:17:43 GMT+0800 (China Standard Time)

Furqanil Taqwa commented a year ago

ReEnMikki · Answer 5 · Wed May 17 2023 07:47:52 GMT+0800 (China Standard Time)

It should have been fixed with this commit: 8a13dce. Please try it and let me know if there is something wrong.
Thank you.

It still doesn't fix the error

Can you confirm it still hasnt fixed? because there is no error in my side, thank you

Yeah, error is still happening for me

Furqanil Taqwa · Answer 6 · Wed May 17 2023 08:12:14 GMT+0800 (China Standard Time)

Are you sure you're not using old notebook commit?

The new condition for quicksettings is :

if "quicksettings" in config:
    config["quicksettings"] = "sd_model_checkpoint, sd_vae, CLIP_stop_at_last_layers, use_old_karras_scheduler_sigmas, always_discard_next_to_last_sigma"
elif "quicksettings_list" in config:
    config["quicksettings_list"] = ["sd_model_checkpoint", "sd_vae", "CLIP_stop_at_last_layers", "use_old_karras_scheduler_sigmas", "always_discard_next_to_last_sigma"]
write_config(config_file, config)

While that line in your console logs was from a991e9b

if config["quicksettings"]:
    config["quicksettings"] = "sd_model_checkpoint, sd_vae, CLIP_stop_at_last_layers, use_old_karras_scheduler_sigmas, always_discard_next_to_last_sigma"
else:
    config["quicksettings_list"] = [
    "sd_model_checkpoint", 
    "sd_vae", 
    "CLIP_stop_at_last_layers", 
    "use_old_karras_scheduler_sigmas", 
    "always_discard_next_to_last_sigma"
    ]

If you're using colab pro please reload the notebook so you can get the latest commit.

ReEnMikki · Answer 7 · Wed May 17 2023 08:38:22 GMT+0800 (China Standard Time)

Are you sure you're not using old notebook commit?

The new condition for quicksettings is :

if "quicksettings" in config:
    config["quicksettings"] = "sd_model_checkpoint, sd_vae, CLIP_stop_at_last_layers, use_old_karras_scheduler_sigmas, always_discard_next_to_last_sigma"
elif "quicksettings_list" in config:
    config["quicksettings_list"] = ["sd_model_checkpoint", "sd_vae", "CLIP_stop_at_last_layers", "use_old_karras_scheduler_sigmas", "always_discard_next_to_last_sigma"]
write_config(config_file, config)

While that line in your console logs was from a991e9b

if config["quicksettings"]:
    config["quicksettings"] = "sd_model_checkpoint, sd_vae, CLIP_stop_at_last_layers, use_old_karras_scheduler_sigmas, always_discard_next_to_last_sigma"
else:
    config["quicksettings_list"] = [
    "sd_model_checkpoint", 
    "sd_vae", 
    "CLIP_stop_at_last_layers", 
    "use_old_karras_scheduler_sigmas", 
    "always_discard_next_to_last_sigma"
    ]

If you're using colab pro please reload the notebook so you can get the latest commit.

Well, it's your official notebook link, and not an old copied one

ReEnMikki · Answer 8 · Wed May 17 2023 08:46:45 GMT+0800 (China Standard Time)

Nevermind, I opened a new tab of this notebook and I see things change like the warning no longer being there. The problem was that while this notebook is still the official one, I kept the tab opening (ever since the problem was still in effect and the old commit still didn't work) and only tried running it again on that same tab of outdated notebook, instead of reloading it to refresh the page for the changes to take effect 🥲

Furqanil Taqwa · Answer 9 · Wed May 17 2023 11:03:07 GMT+0800 (China Standard Time)

Yeah, sorry. I pushed so many commits today, and probably it got fixed while you were still viewing the last updated commit.
Also, sometimes there can be a delay in reflecting the changes after the commit has already been pushed to GitHub

sleel · Answer 10 · Wed May 17 2023 11:25:25 GMT+0800 (China Standard Time)

Yeah, sorry. I pushed so many commits today, and probably it got fixed while you were still viewing the last updated commit. Also, sometimes there can be a delay in reflecting the changes after the commit has already been pushed to GitHub

it works Thank you so much!