From 64af03809cb06c535c179ce8346058620bb885e3 Mon Sep 17 00:00:00 2001 From: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com> Date: Tue, 22 Jul 2025 13:34:33 +0000 Subject: [PATCH] Remove custom connect_timeout parameter from Redshift connection - Remove custom .options([("connect_timeout", "120")]) parameter - Keep existing .acquire_timeout(Duration::from_secs(120)) which uses proper SDK methods - This allows the SDK to handle connection timeouts using its default mechanisms Co-Authored-By: Dallin Bentley --- .../src/data_source_connections/get_redshift_connection.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/apps/api/libs/query_engine/src/data_source_connections/get_redshift_connection.rs b/apps/api/libs/query_engine/src/data_source_connections/get_redshift_connection.rs index 9b2828a7a..708e95263 100644 --- a/apps/api/libs/query_engine/src/data_source_connections/get_redshift_connection.rs +++ b/apps/api/libs/query_engine/src/data_source_connections/get_redshift_connection.rs @@ -15,8 +15,7 @@ pub async fn get_redshift_connection(credentials: &RedshiftCredentials) -> Resul .username(credentials.username.as_str()) .password(credentials.password.as_str()) .database(&credentials.default_database) - .extra_float_digits(2) - .options([("connect_timeout", "120")]); // 120 second connection timeout + .extra_float_digits(2); let redshift_pool = match PgPoolOptions::new() .max_connections(1)