Skip to content

Clear throttle cache on ConsumerThrottleLimit.save #150

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

Merged
merged 2 commits into from
Apr 25, 2025

Conversation

mbertrand
Copy link
Member

What are the relevant tickets?

Closes https://github.com/mitodl/hq/issues/7107

Description (What does it do?)

Overrides the ConsumerThrottleLimit.save function to clear the throttle cache.

Screenshots (if appropriate):

  • Desktop screenshots
  • Mobile width screenshots

How can this be tested?

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @mbertrand, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request addresses issue #7107 by modifying the ConsumerThrottleLimit model to clear the throttle cache whenever an instance of the model is saved. This ensures that changes to throttle limits are immediately reflected in the application's behavior. The changes involve overriding the save method of the ConsumerThrottleLimit model to delete the CONSUMER_THROTTLES_KEY from the cache. Additionally, a test case has been added to verify that the cache is indeed cleared when the model is saved.

Highlights

  • Cache Invalidation: The primary goal is to invalidate the consumer throttles cache whenever a ConsumerThrottleLimit model is saved, ensuring that the most up-to-date throttle configurations are used.
  • Model Override: The save method of the ConsumerThrottleLimit model is overridden to include cache invalidation logic.
  • Test Coverage: A new test case is added to verify that saving a ConsumerThrottleLimit model clears the cache as expected.

Changelog

Click here to see the changelog
  • main/constants.py
    • Added CONSUMER_THROTTLES_KEY constant to store the key used for caching consumer throttles. This constant is used to invalidate the cache when throttle limits are updated. (line 16)
  • main/consumer_throttles.py
    • Imported CONSUMER_THROTTLES_KEY from main.constants to be used for cache invalidation. (line 15)
    • Removed the duplicate definition of CONSUMER_THROTTLES_KEY as it is now defined in main/constants.py. (line 21)
  • main/models.py
    • Imported cache from django.core.cache to allow cache operations within the model. (line 5)
    • Imported CONSUMER_THROTTLES_KEY from main.constants to be used for cache invalidation. (line 9)
    • Overrode the save method to delete the CONSUMER_THROTTLES_KEY from the cache before saving the model. (lines 83-86)
  • main/models_test.py
    • Added a new test case test_throttle_limit_save_reset_cache to verify that saving a ConsumerThrottleLimit model clears the cache. (lines 10-39)
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A cache we keep with care,
Throttle limits stored with flair,
But when they change,
A quick arrange,
To clear the cache, beyond compare.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces a mechanism to clear the throttle cache whenever a ConsumerThrottleLimit object is saved. This ensures that changes to throttle limits are reflected immediately, which is great. The implementation includes a test case to verify this behavior. Overall, the changes look good, but I have a few suggestions.

Summary of Findings

  • Cache invalidation on save: The save method of the ConsumerThrottleLimit model is overridden to delete the CONSUMER_THROTTLES_KEY from the cache, ensuring that throttle limits are refreshed when the model is updated.
  • Test case for cache invalidation: A test case test_throttle_limit_save_reset_cache is added to verify that saving changes to the ConsumerThrottleLimit model resets the cache as expected.

Merge Readiness

The code changes seem correct and the included test case provides confidence in the implementation. I recommend merging this pull request after addressing the comments below. I am unable to directly approve the pull request, and users should have others review and approve this code before merging.

@abeglova abeglova self-assigned this Apr 24, 2025
Copy link
Contributor

@abeglova abeglova left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@mbertrand mbertrand force-pushed the mb/change_throttle_on_save branch from f2d1a67 to e7ab93d Compare April 25, 2025 12:09
@mbertrand mbertrand merged commit 976c7c8 into main Apr 25, 2025
7 checks passed
This was referenced Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants