-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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
Add progress bar #9983
Conversation
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, only one small comment
@@ -19,7 +19,7 @@ const FetchMessage = styled.div` | |||
|
|||
const LoadingSchema: React.FC = () => ( | |||
<SpinnerBlock> | |||
<Spinner /> | |||
<ProgressBar runTime={120} /> |
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.
Can we make this 4min when running discover? 2min seems good for check connection.
@@ -19,7 +19,7 @@ const FetchMessage = styled.div` | |||
|
|||
const LoadingSchema: React.FC = () => ( | |||
<SpinnerBlock> | |||
<Spinner /> | |||
<ProgressBar runTime={240} /> |
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.
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.
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.
Hehe, I believe we need to ask @jrhizor for such info.
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.
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.
Co-authored-by: Tim Roes <mail@timroes.de>
Co-authored-by: Jared Rhizor <jared@dataline.io>
What
Add Progress Bar for checking connection and running the discover schema
If the ProgressBar is full and process has not ended, the message will appear.
Closes #9756