Remove connectionTimeoutMillis from pool options#9725
Conversation
Summary of ChangesHello @fredzqm, 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 addresses a reported regression by reverting a recent change that introduced a specific connection timeout setting. By removing the Highlights
🧠 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 AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request addresses a regression by removing the connectionTimeoutMillis setting from the PostgreSQL connection pool options. By reverting to the default behavior of node-postgres (which has no timeout for acquiring a connection), this change should resolve the connection issues introduced by the explicit 1-second timeout. The change is simple, targeted, and appears to be the correct fix for the described problem.
Description
Discussions suggested that we introduced a regression since 14.17.0
#9314 (comment)
The timeout was added in #9200. The only change to
connect.tssince 14.17.0.Scenarios Tested
Sample Commands