-
Notifications
You must be signed in to change notification settings - Fork 88
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: GoogleCloudPlatform/cloud-sql-python-connector
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.10.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: GoogleCloudPlatform/cloud-sql-python-connector
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.11.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 15 commits
- 21 files changed
- 5 contributors
Commits on Jun 14, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 2eeffee - Browse repository at this point
Copy the full SHA 2eeffeeView commit details
Commits on Jun 19, 2024
-
Configuration menu - View commit details
-
Copy full SHA for fe2ccb8 - Browse repository at this point
Copy the full SHA fe2ccb8View commit details
Commits on Jun 25, 2024
-
feat: invalidate cache on bad connection info and IP lookup (#1118)
The Connector caches connection info for future connections and schedules refresh operations, however for unrecoverable errors/state we should invalidate the cache to stop future bad refreshes. We should invalidate the cache on all failed calls to the Cloud SQL Admin APIs, as well as failed IP lookup (preferred IP does not exist). Added a ._remove_cached method to the Connector to facilitate invalidating the cache.
Configuration menu - View commit details
-
Copy full SHA for 672dc4e - Browse repository at this point
Copy the full SHA 672dc4eView commit details -
Configuration menu - View commit details
-
Copy full SHA for ab253ea - Browse repository at this point
Copy the full SHA ab253eaView commit details -
Configuration menu - View commit details
-
Copy full SHA for f48eae1 - Browse repository at this point
Copy the full SHA f48eae1View commit details
Commits on Jun 26, 2024
-
fix: let DNS resolve outside connector (#1120)
Python's SSLContext requires trailing dot to be stripped from DNS names in order to properly configure SSL/TLS. Previously, we were resolving the DNS and connecting to the PSC endpoint within the Connector. However, this was a poor workaround as we should really just strip the trailing dot and allow the drivers to resolve the DNS on connection.
Configuration menu - View commit details
-
Copy full SHA for d321f79 - Browse repository at this point
Copy the full SHA d321f79View commit details
Commits on Jul 4, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 2cf9c66 - Browse repository at this point
Copy the full SHA 2cf9c66View commit details
Commits on Jul 5, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 31c491c - Browse repository at this point
Copy the full SHA 31c491cView commit details
Commits on Jul 8, 2024
-
Configuration menu - View commit details
-
Copy full SHA for d1147e9 - Browse repository at this point
Copy the full SHA d1147e9View commit details
Commits on Jul 9, 2024
-
Configuration menu - View commit details
-
Copy full SHA for bbb83a9 - Browse repository at this point
Copy the full SHA bbb83a9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 076da83 - Browse repository at this point
Copy the full SHA 076da83View commit details
Commits on Jul 10, 2024
-
fix: retry 50x errors with exponential backoff (#1125)
This commit adds retry behavior to the two SQL Admin API calls. Any response that results in a 50x error will now be retried up to 5 times with exponential backoff and jitter between each attempt. The formula used to calculate the duration to wait is: 200ms * 1.618^(attempt + jitter) This calculation matches what the Cloud SQL Proxy v1 did and will not trigger any significant change in load on the backend.
Configuration menu - View commit details
-
Copy full SHA for 2da9128 - Browse repository at this point
Copy the full SHA 2da9128View commit details -
Configuration menu - View commit details
-
Copy full SHA for e3e3ff2 - Browse repository at this point
Copy the full SHA e3e3ff2View commit details -
Configuration menu - View commit details
-
Copy full SHA for b415160 - Browse repository at this point
Copy the full SHA b415160View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9583c94 - Browse repository at this point
Copy the full SHA 9583c94View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v1.10.0...v1.11.0