-
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
feat(ui, worker): add invocation progress events to model loading #7286
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
maryhipp
requested review from
psychedelicious,
blessedcoolant,
hipsterusername and
brandonrising
as code owners
November 7, 2024 01:36
github-actions
bot
added
python
PRs that change python files
services
PRs that change app services
frontend
PRs that change frontend files
python-tests
PRs that change python tests
labels
Nov 7, 2024
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.
Probably also want events around the download_and_cache_model
psychedelicious
force-pushed
the
maryhipp/invocation-progress-ui
branch
from
November 14, 2024 18:39
683d3b9
to
fccc87a
Compare
- Pass in the `UtilInterface` to the `ModelsInterface` so we can call the simple `signal_progress` method instead of the complicated `emit_invocation_progress` method. - Only emit load events when starting to load - not after. - Add more detail to the messages, like submodel type
- Tweak layout/styling of alerts for consistent spacing - Add percentage to message if it has percentage - Only show events if the destination is canvas (so workflows events are hidden for example)
- Add `invocationProgressAlert` as a disable-able feature. Hide the alert and the setting in system settings when disabled. - Fix merge conflict
psychedelicious
force-pushed
the
maryhipp/invocation-progress-ui
branch
from
November 14, 2024 18:39
fccc87a
to
283a966
Compare
psychedelicious
approved these changes
Nov 14, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
frontend
PRs that change frontend files
invocations
PRs that change invocations
python
PRs that change python files
python-tests
PRs that change python tests
services
PRs that change app services
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Related Issues / Discussions
QA Instructions
Invoke to either gallery or canvas, see invocation progress details (model loading, denoising)
Merge Plan
Checklist
What's New
copy (if doing a release after this PR)