You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd ask for a way to terminate the server that is not Ctrl-C.
Reasoning: On Windows, stopping a program with Ctrl-C also interrupts the batch file(s) calling that program, making them ask for confirmation. This is quite annoying, especially because InvokeAI has its "what do you want to do" wrapper. With my own "start in a conda environment" wrapper, that's three prompts.
I much prefer to press any other key combination to land directly in the InvokeAI wrapper without the batch spam.
Alternatives
A button in the UI to stop or restart would be nice, too. But hosting and stuff...
Additional Content
Not worth its own issue: How about a config to auto-restart when "VRAM in use" after a generation doesn't go down to a reasonable level? That's the most common failure mode that forces me to Ctrl-C in the first place.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Contact Details
No response
What should this feature add?
I'd ask for a way to terminate the server that is not Ctrl-C.
Reasoning: On Windows, stopping a program with Ctrl-C also interrupts the batch file(s) calling that program, making them ask for confirmation. This is quite annoying, especially because InvokeAI has its "what do you want to do" wrapper. With my own "start in a conda environment" wrapper, that's three prompts.
I much prefer to press any other key combination to land directly in the InvokeAI wrapper without the batch spam.
Alternatives
A button in the UI to stop or restart would be nice, too. But hosting and stuff...
Additional Content
Not worth its own issue: How about a config to auto-restart when "VRAM in use" after a generation doesn't go down to a reasonable level? That's the most common failure mode that forces me to Ctrl-C in the first place.
The text was updated successfully, but these errors were encountered: