-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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(cache): Fix two bugs in Admin / Performance #44255
Conversation
This stack of pull requests is managed by Graphite. Learn more about stacking. |
b738277
to
2a6d189
Compare
Graphite Automations"Warn authors when publishing large PRs" took an action on this PR • (06/14/24)1 teammate was notified to this PR based on Raphael Krut-Landau's automation. |
|
2a6d189
to
f20ab3b
Compare
0055de3
to
880026f
Compare
frontend/src/metabase/admin/performance/hooks/useSaveStrategy.tsx
Outdated
Show resolved
Hide resolved
- When adaptive policy is saved, it's not shown on the page - 12:00PM cannot be used as a time in the Schedule component - Clear cache when switching strategy to "Don't cache results"
…tion which also fixes the failing unit test
40fdac1
to
35bed5c
Compare
#44249 Still seems to be broken |
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.
Checked that the issues mentioned were resolved, and they seem to be. I don't entirely follow all the conversion logic though. Will catch up with @rafpaf when he's back to get an overview
Nick has now approved this PR after Sloan's changes
* fix(cache): Fix two bugs in Admin / Performance (#44255) Ensures that minimum query durations are correctly displayed in the form post-save (#44249) and that all times can be used in the Schedule component (#44257) --------- Co-authored-by: Raphael Krut-Landau <[email protected]>
Closes #44249: When a new minimum query duration is added to an adaptive policy, it disappears from the form on save.
Closes #44257: Aberrant edge case: 12:00PM cannot be used as a time in the Schedule component.