fix: extended session usage using LRU cache

[RahulLanjewar93]

…y clear memory and functions as a debounce instead of a throttle (parse-community#8683)

Pull Request

• Report security issues confidentially.
• Any contribution is under this license.
• Link this pull request to an issue.

Issue

Closes: FILL_THIS_OUT

Approach

Tasks

• Add tests
• Add changes to documentation (guides, repository pages, code comments)
• Add security check
• Add new Parse Error codes to Parse JS SDK

[gemini-code-assist]

Summary of Changes

Hello @RahulLanjewar93, I'm Gemini Code Assist¹! 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!

I've implemented a fix to improve the extended session usage mechanism. This change refines how session renewals are throttled, moving from a less precise 'setTimeout' based approach to a more robust LRU cache-based system. This ensures that session expiry is updated efficiently and reliably, preventing unnecessary database writes while maintaining session validity for active users.

Highlights

• Session Renewal Logic Refinement: I've updated the 'renewSessionIfNeeded' function in 'src/Auth.js' to utilize an LRU cache for managing session renewal requests.
• Improved Throttling Mechanism: The previous 'setTimeout' based throttling has been replaced with an LRU cache, which acts as a debounce, ensuring that session expiry is extended only when truly needed and preventing rapid, redundant updates.
• Enhanced Test Reliability: In 'spec/Auth.spec.js', I've added 'Parse.Server.cacheController.clear()' and a delay to ensure that tests for session renewal are more reliable and accurately reflect the new throttling behavior by clearing any cached states.

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 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 or fill out our survey 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.

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. ↩

[gemini-code-assist]

Code Review

This pull request replaces the session renewal throttling mechanism, which used setTimeout, with a debouncing mechanism using lru-cache. This change is intended to prevent session renewal on every request, instead doing it once and then ignoring subsequent requests for a short period. The implementation looks correct, but I have a couple of suggestions. First, the variable name throttle is now misleading and should be renamed to reflect the new debouncing behavior. Second, the related test uses setTimeout which can make it slow and flaky; I recommend refactoring it to use fake timers for better reliability and speed.