Permalink
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.
...
- 11 commits
- 14 files changed
- 6 contributors
Commits on Nov 13, 2024
Commits on Nov 16, 2024
-
feat: invalidate cache on bad connection info and failed IP lookup (#389
) This change is analogous to CloudSQL's GoogleCloudPlatform/cloud-sql-python-connector#1118. The Connector caches connection info for future connections and schedules refresh operations. For unrecoverable errors, the cache should be invalidated to stop future bad refreshes. The cache should also be invalidated on failed IP lookups. This PR does these things.
Commits on Nov 18, 2024
-
chore: use sync instead of async in test (#396)
`test_Connector_remove_cached_bad_instance` doesn't need to be async, because it can use the event loop that is generated by `Connector.__init__()` function.
Commits on Dec 4, 2024
-
feat: improve aiohttp client error messages (#400)
This change is similar to GoogleCloudPlatform/cloud-sql-python-connector#1201, except for AlloyDB.
Commits on Dec 5, 2024
Commits on Dec 10, 2024
-
-
chore(deps): bump aiohttp from 3.10.10 to 3.10.11 (#394)
Bumps [aiohttp](https://github.com/aio-libs/aiohttp) from 3.10.10 to 3.10.11. - [Release notes](https://github.com/aio-libs/aiohttp/releases) - [Changelog](https://github.com/aio-libs/aiohttp/blob/master/CHANGES.rst) - [Commits](aio-libs/aiohttp@v3.10.10...v3.10.11) --- updated-dependencies: - dependency-name: aiohttp dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
-
-
-
chore(main): release 1.6.0 (#393)
Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
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.5.0...v1.6.0