feat: add redis distribute lock

[fatelei]

Description

Please provide a brief description of the changes made in this pull request.
Please also include the issue number if this is related to an issue using the format Fixes #123 or Closes #123.

fix #541

Type of Change

• Bug fix
• New feature
• Refactor
• Performance improvement
• Other

Essential Checklist

Testing

• I have tested the changes locally and confirmed they work as expected
• I have added unit tests where necessary and they pass successfully

Bug Fix (if applicable)

• I have used GitHub syntax to close the related issue (e.g., Fixes #123 or Closes #123)

Additional Information

Please provide any additional context that would help reviewers understand the changes.

[gemini-code-assist]

Summary of Changes

Hello @fatelei, 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!

This pull request implements a robust distributed locking mechanism using Redis to safeguard the critical process of initializing Python virtual environments for local plugins. By preventing concurrent modifications to these environments across different instances or pods, the changes significantly enhance the stability and integrity of plugin deployments, resolving potential race conditions and ensuring consistent setup.

Highlights

• Distributed Locking for Python Environments: Introduced a Redis-based distributed locking mechanism to prevent race conditions during the initialization of Python virtual environments for local plugins.
• Enhanced Environment Stability: The distributed lock ensures that only one process or pod can create or modify a specific Python virtual environment at a time, improving the reliability and consistency of plugin setups.
• New Redis Lock Utilities: Added Lock and Unlock functions within the pkg/utils/cache package to manage distributed locks.
• Comprehensive Testing: Included a new test file (pkg/utils/cache/redis_lock_test.go) utilizing miniredis to thoroughly validate the distributed lock's exclusive acquisition and timeout behavior.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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 introduces a Redis-based distributed lock to prevent race conditions during the initialization of Python virtual environments. This is a good approach to ensure safety in a multi-pod environment. The implementation is straightforward and includes a new unit test for the lock. My main concern is with the timeout configuration for the lock. The current values are very long and could impact service availability if a pod holding a lock crashes. I've provided a suggestion to make the timeouts more robust.