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
Bug 1877368: Disable Helm Chart Install form and show error alert if chart is not reachable #6572
Bug 1877368: Disable Helm Chart Install form and show error alert if chart is not reachable #6572
Conversation
/assign @rohitkrai03 |
} catch {} // eslint-disable-line no-empty | ||
} catch (e) { | ||
error = e; | ||
} // eslint-disable-line no-empty | ||
if (ignore) return; |
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.
just a query. Why do we have this ignore
check after the coFetch and not before it?
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.
Okay I will try to explain it briefly. So we do this to prevent updating a state of an unmounted component and as you can see the state is being updated only after the API call. If a component is unmounted then anyways a new API call cannot be made but this helps when a call is already made but the response has not yet been received and the component unmounts before that, so when the call returns we prevent the state from being updated.
@divyanshiGupta: This pull request references Bugzilla bug 1877368, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
9beefa1
to
0d9511c
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.
I think chart version dropdown should be hidden if there's no chart version present. Empty dropdown feels odd here. @parvathyvr WDYT?
Do we have placeholders? I wonder if "No versions available" or something akin to that is better... Just wondering if removing the input item, labels et all is going to leave more of a void in the UI. |
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.
I agree with @rohitkrai03 that the empty dropdown looks odd.In the original mockup screen attached in the bug ODC-4360 I had the Chart Version dropdown although disabled ,showing the latest chart version/app version.But if we do not have this data to show, my opinion would be in lines with what @andrewballantyne suggested above.I think if we do not have data to show in the ‘Chart Version’ dropdown we can show ‘Not available’ in the disabled dropdown. CC @beaumorley
@parvathyvr I will add the |
@parvathyvr Do you think we should also add the http error that we get back from backend to the alert. I tried it with a private helm chart that is not accessible and it looks something like this - |
0d9511c
to
d83f432
Compare
@divyanshiGupta: This pull request references Bugzilla bug 1877368, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rohitkrai03 I think giving more info about why the Helm chart is unavailable is a good addition!
|
d83f432
to
57dc4a7
Compare
@divyanshiGupta: This pull request references Bugzilla bug 1877368, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rohitkrai03 @parvathyvr done. PTAL. |
57dc4a7
to
2b40b80
Compare
@divyanshiGupta: This pull request references Bugzilla bug 1877368, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
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.
/approve
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!
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: divyanshiGupta, parvathyvr, rohitkrai03 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest Please review the full test history for this PR and help us cut down flakes. |
11 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest |
@divyanshiGupta: This pull request references Bugzilla bug 1877368, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
/retest Please review the full test history for this PR and help us cut down flakes. |
@divyanshiGupta: All pull requests linked via external trackers have merged: Bugzilla bug 1877368 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Jira: https://issues.redhat.com/browse/ODC-4360
Fixes #5190
Screenshot:
Unit Tests Coverage:
/kind bug