Repository navigation
Conversation
…ps when older than a configurable time interval. #12809
|
|
📦 Pushed preview images as 🚢 See on GHCR. Use by referencing with full name as printed above, mind the registry name. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


What this PR does / why we need it:
Please see #12809, it's fairly straightforward.
Which issue(s) this PR closes:
Special notes for your reviewer:
The logic that decides whether to proceed with updating the timestamp or not is within a method with a "requires new" transaction attribute. Meaning there will always be, at least an empty, extra transaction after every call. Like most of the PR, this was an ai-recommended solution. With the following rationale provided:
Which seemed reasonable to me.
Suggestions on how to test this:
Enable the feature flag (see the accompanying docs); run some api methods with valid API tokens of different users. Check the
lastApiUseTimein theAuthenticatedUsertable, with and without a specific (non-default) refresh interval configured.Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
yes. included.
Additional documentation: