-
Notifications
You must be signed in to change notification settings - Fork 356
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: historical-usage date calculation bug #9257
Conversation
✅ Deploy Preview for determined-ui ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #9257 +/- ##
==========================================
- Coverage 44.71% 38.00% -6.71%
==========================================
Files 1271 947 -324
Lines 155397 115741 -39656
Branches 2436 2437 +1
==========================================
- Hits 69487 43993 -25494
+ Misses 85673 71511 -14162
Partials 237 237
Flags with carried forward coverage won't be shown. Click here to find out more.
|
7e2e270
to
5c98f31
Compare
@@ -53,32 +54,34 @@ const ClusterHistoricalUsageFilters: React.FC<ClusterHistoricalUsageFiltersProps | |||
|
|||
const handleAfterDateSelect = (afterDate: Dayjs | null) => { | |||
if (!afterDate) return; | |||
const val = _.cloneDeep(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.
value
from props should not be directly modified.
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.
Works as expected
(cherry picked from commit 8794e42)
Ticket
DET-10249
Description
value
prop was directly modified in calendar onChange handler. That caused unintentional state change.Test Plan
/clusters/historical-usage
from
range too far (more than a year) with group byday
andmonths
start date cannot be after end date
error is not shown and correctly call/api/v1/resources/allocation/aggregated
APIChecklist
docs/release-notes/
.See Release Note for details.