-
Notifications
You must be signed in to change notification settings - Fork 64
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
fix(Staleness): Update staleness page to match new backend specs #2082
Conversation
19a7b0b
to
f940b0c
Compare
f940b0c
to
09ed3c7
Compare
/retest |
Codecov ReportAttention:
📢 Thoughts on this report? Let us know! |
003bfde
to
c773d07
Compare
/retest |
2 similar comments
/retest |
/retest |
/retest |
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, the PR works just fine, and all the bugs/changes associated with the tickets are resolved. There is a flaky test failure, otherwise everything passes so you can ignore the travis check for now
if (seconds === 104400) { | ||
return 1; | ||
} else { | ||
return seconds / 86400; |
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.
Maybe we better have some rounding? In case backend provides malformed data/something goes wrong and we at least provide an integer value.
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.
The requirement for this day in particular requires a a buffer, originally this was just one day/86400 seconds, but they want this specific buffer going forward
@computercamplove those reset values come from the api, Once the backend makes the appropriate changes and sends them to stage, the changes will reflect on the FE |
🎉 This PR is included in version 1.55.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This PR adds an additional check to only send values that have been altered to the api.
It also removes 'unknown' as an option for the status filter.
fix(RHINENG-2911): Update values in staleness api request
fix(ESSNTL-5595): remove unknown option in status filter
ESSNTL-5538: Update RBAC roles & Add buffer to api Values
https://issues.redhat.com/browse/ESSNTL-5605 : [UI] Update custom staleness defaults for edge systems