-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[#6333] Add clear_queue_on_startup config to clear problematic queues #6502
[#6333] Add clear_queue_on_startup config to clear problematic queues #6502
Conversation
be3d2c4
to
0063dcb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! And sorry for the late review. I've requested some changes.
dc896b2
to
5b6ef66
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good! I just realized that the logging of the clear/prune result needs to be updated. Good to merge after that is fixed.
aab4e61
to
3f408c0
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks again!
3f408c0
to
eb2168f
Compare
Summary
Simple fix to clear problematic queues on startups leading to crashes by adding
empty_queue_on_startup
config toinvokeai.yaml
Related Issues / Discussions
Closes #6333
Checklist