-
Notifications
You must be signed in to change notification settings - Fork 156
deploy: Add a spinner #848
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
Conversation
In some cases I wasn't seeing this output, and I think it's because we hadn't `drop()`'d the bar. Since it's in scope it's cleaner to use its `println` method. Signed-off-by: Colin Walters <[email protected]>
First, this operation was absolutely not asynchronous and we need to spawn it in a helper thread on general principle. Doing that is unfortunately VERY hacky because we need to clone a lot of things and especially there's an ergonomics hit here since `Deployment` is incorrectly `!Send`. But the main motivation is this operation can be slow sometimes, so let's show progress output so the admin knows we're not blocked. Closes: bootc-dev#842 Signed-off-by: Colin Walters <[email protected]>
vrothberg
left a comment
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.
LGTM
omertuc
left a comment
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.
looks good except for one question
|
/lgtm |
|
Oh and FYI, IDK if you care but you added |
Things we do via this mechanism can take some time; let's log the elapsed time for greater visibility both to the human output *and* log to the journal. Signed-off-by: Colin Walters <[email protected]>
adc37ab to
daeafea
Compare
I dropped that |
This repository doesn't use Prow, so to merge it needs a Github approval state |
deploy: Use bar.println
In some cases I wasn't seeing this output, and I think it's
because we hadn't
drop()'d the bar. Since it's in scopeit's cleaner to use its
printlnmethod.Signed-off-by: Colin Walters [email protected]
deploy: Add a spinner
First, this operation was absolutely not asynchronous
and we need to spawn it in a helper thread on general
principle. Doing that is unfortunately VERY hacky
because we need to clone a lot of things and especially
there's an ergonomics hit here since
Deploymentisincorrectly
!Send.But the main motivation is this operation can be slow sometimes,
so let's show progress output so the admin knows we're not blocked.
Closes: #842
Signed-off-by: Colin Walters [email protected]
utils: Print and log time for async_task_with_spinner
Things we do via this mechanism can take some time; let's
log the elapsed time for greater visibility both to the
human output and log to the journal.
Signed-off-by: Colin Walters [email protected]