Skip to content

Add WEB_SERVER_GUNICORN_WAIT env var for slow systems#2887

Merged
gantoine merged 3 commits intomasterfrom
web-server-gunicorn-retries
Jan 11, 2026
Merged

Add WEB_SERVER_GUNICORN_WAIT env var for slow systems#2887
gantoine merged 3 commits intomasterfrom
web-server-gunicorn-retries

Conversation

@gantoine
Copy link
Copy Markdown
Member

Description
Explain the changes or enhancements you are proposing with this pull request.

This PR allows users with slower systems to set the gunicorn wait time on bootup with WEB_SERVER_GUNICORN_WAIT

Checklist
Please check all that apply.

  • I've tested the changes locally
  • I've updated relevant comments
  • I've assigned reviewers for this PR
  • I've added unit tests that cover the changes

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

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

This pull request enhances the application's startup process by introducing a new environment variable, WEB_SERVER_GUNICORN_RETRIES. This variable allows users to configure the number of retries for the Gunicorn web server socket to become available, providing flexibility for systems with varying boot times and preventing premature startup failures. The change effectively makes the Gunicorn wait time configurable, as implied by the PR title, through the number of retries.

Highlights

  • Configurable Gunicorn Socket Retries: Introduces the WEB_SERVER_GUNICORN_RETRIES environment variable, allowing users to customize the number of retry attempts for the Gunicorn socket to become available during application startup. This addresses the need for slower systems to have more time for Gunicorn to initialize.
  • Default Retry Count: The wait_for_gunicorn_socket function now defaults to 60 retries if WEB_SERVER_GUNICORN_RETRIES is not explicitly set, maintaining the previous 30-second wait period (60 retries * 0.5s sleep).
  • Generic Warning Message: The warning message issued when the Gunicorn socket is not found after waiting has been updated to be more general, removing the specific "30s" reference.
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.

Copy link
Copy Markdown
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 an environment variable to configure the Gunicorn socket wait time, which is helpful for slower systems. My review focuses on improving the clarity and usability of this new setting. I've suggested renaming the environment variable from WEB_SERVER_GUNICORN_RETRIES to WEB_SERVER_GUNICORN_WAIT_SECONDS to make its purpose more intuitive and align it with the pull request's description. This change also allows for a more informative warning message if the socket isn't found in time. I've provided code suggestions for both the init script and the env.template file to implement this.

@gantoine
Copy link
Copy Markdown
Member Author

/gemini review

Copy link
Copy Markdown
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 the WEB_SERVER_GUNICORN_WAIT_SECONDS environment variable to allow users to configure the wait time for the gunicorn socket, which is a helpful addition for systems that may be slow to start services. The implementation is clear and addresses the problem statement.

I've added one comment with a suggestion to improve the script's robustness by validating the new environment variable.

As a minor point, the PR title and description mention WEB_SERVER_GUNICORN_WAIT, while the code and env.template use the more descriptive WEB_SERVER_GUNICORN_WAIT_SECONDS. It would be good to update the PR's text to match the code for consistency.

@gantoine gantoine merged commit 3c27b71 into master Jan 11, 2026
6 checks passed
@gantoine gantoine deleted the web-server-gunicorn-retries branch January 11, 2026 04:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant