Skip to content
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

Add progress bar #9983

Merged
merged 7 commits into from
Feb 3, 2022
Merged

Add progress bar #9983

merged 7 commits into from
Feb 3, 2022

Conversation

juliachvyrova
Copy link
Contributor

What

Add Progress Bar for checking connection and running the discover schema

Снимок экрана 2022-02-02 в 01 18 51

If the ProgressBar is full and process has not ended, the message will appear.
Снимок экрана 2022-02-02 в 01 19 53

Closes #9756

@github-actions github-actions bot added area/frontend area/platform issues related to the platform labels Feb 1, 2022
@juliachvyrova juliachvyrova self-assigned this Feb 1, 2022
Copy link
Contributor

@jrhizor jrhizor left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, only one small comment

@@ -19,7 +19,7 @@ const FetchMessage = styled.div`

const LoadingSchema: React.FC = () => (
<SpinnerBlock>
<Spinner />
<ProgressBar runTime={120} />
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make this 4min when running discover? 2min seems good for check connection.

@juliachvyrova juliachvyrova temporarily deployed to more-secrets February 2, 2022 23:08 Inactive
@@ -19,7 +19,7 @@ const FetchMessage = styled.div`

const LoadingSchema: React.FC = () => (
<SpinnerBlock>
<Spinner />
<ProgressBar runTime={240} />
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we please leave an inline comment here in code how we got to this rather arbitrary number? Like that this is an experience based amount of time this task usually runs, but so we'll be able in the future to understand where this number was coming from.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hehe, I believe we need to ask @jrhizor for such info.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This number just is purely a middle-of-the-road estimate based off of personal experiences running checks/discover across docker-compose OSS / kube OSS / cloud. In the future we can tune this based off of run durations when we actually capture them.

juliachvyrova and others added 2 commits February 3, 2022 20:19
Co-authored-by: Tim Roes <mail@timroes.de>
@juliachvyrova juliachvyrova temporarily deployed to more-secrets February 3, 2022 17:22 Inactive
Co-authored-by: Jared Rhizor <jared@dataline.io>
@jamakase jamakase temporarily deployed to more-secrets February 3, 2022 18:41 Inactive
@jamakase jamakase merged commit a938c4d into master Feb 3, 2022
@jamakase jamakase deleted the julia/add-progress-bar branch February 3, 2022 20:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/platform issues related to the platform
Projects
None yet
Development

Successfully merging this pull request may close these issues.

add a progress bar for running the check connection and discover commands
4 participants