-
Notifications
You must be signed in to change notification settings - Fork 348
Comparing changes
Open a pull request
base repository: googleapis/google-auth-library-python
base: v1.19.2
head repository: googleapis/google-auth-library-python
compare: v1.20.0
- 7 commits
- 34 files changed
- 6 contributors
Commits on Jul 21, 2020
-
feat: Add debug logging that can help with diagnosing auth lib. path (#…
…473) Co-authored-by: Bu Sun Kim <8822365+busunkim96@users.noreply.github.com> Co-authored-by: Tres Seaver <tseaver@palladion.com>
Configuration menu - View commit details
-
Copy full SHA for ecd88d4 - Browse repository at this point
Copy the full SHA ecd88d4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 18d5ae6 - Browse repository at this point
Copy the full SHA 18d5ae6View commit details -
feat: Show the transport exception that happened for GCE Metadata (#474)
Two primary motivators here: 1. Why obscure the exception? Sometimes it has some really useful information, such as the case when its being rate limited or throwing some internal error. Some of those responses have valuable information; and it's a public API so the contents of it are not a secret. 2. The metadata server should not be spewing failures that often; I think it would be good to know with `WARNING` when it happens since `WARNING` is the default and what a lot of people run with. When Metadata servers have issues overnight, we have no logs for those who left it as default. A good example of this is when the Metadata server is being rate limited; it would be good to know that's happening. Logs will help make that faster, though ideally of course maybe the library would have a result or something indicating the status of all checks (or something else so faults can be diagnosed faster?) but logs are cheap, easy and make diagnosing it a lot faster. It should be rare enough (correct me if I'm wrong?) that it should not be failing often enough except in the "resolution lag" case.
Configuration menu - View commit details
-
Copy full SHA for 23919bb - Browse repository at this point
Copy the full SHA 23919bbView commit details -
chore: update kokoro config (via synth) (#556)
This PR was generated using Autosynth. 🌈 Synth log will be available here: https://source.cloud.google.com/results/invocations/abd11f9f-00ea-4883-9679-79e339a91948/targets - [ ] To automatically regenerate this PR, check this box. Source-Link: googleapis/synthtool@ffe1040
Configuration menu - View commit details
-
Copy full SHA for d91c24c - Browse repository at this point
Copy the full SHA d91c24cView commit details -
chore(deps): update dependency rsa to <4.6 (#544)
This PR contains the following updates: | Package | Update | Change | |---|---|---| | [rsa](https://stuvel.eu/rsa) | minor | `<4.1` -> `<4.7` | --- ### Renovate configuration :date: **Schedule**: At any time (no schedule defined). :vertical_traffic_light: **Automerge**: Disabled by config. Please merge this manually once you are satisfied. :recycle: **Rebasing**: Renovate will not automatically rebase this PR, because other commits have been found. :no_bell: **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [WhiteSource Renovate](https://renovate.whitesourcesoftware.com). View repository job log [here](https://app.renovatebot.com/dashboard#googleapis/google-auth-library-python).
Configuration menu - View commit details
-
Copy full SHA for 6dd2597 - Browse repository at this point
Copy the full SHA 6dd2597View commit details
Commits on Jul 23, 2020
-
feat(packaging): add support for Python 3.8 (#569)
Release-As: 1.20.0 Closes #568
Configuration menu - View commit details
-
Copy full SHA for 1aad54a - Browse repository at this point
Copy the full SHA 1aad54aView commit details
Commits on Jul 28, 2020
-
Configuration menu - View commit details
-
Copy full SHA for 8e45f0b - Browse repository at this point
Copy the full SHA 8e45f0bView commit details
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.19.2...v1.20.0