-
Notifications
You must be signed in to change notification settings - Fork 250
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
StackdriverExporter with application default credentials crashes #304
Comments
@ocervell thank you for filing this issue. I see you mailed out PR #291 which was merged. Is this issue still a problem? Kindly paging @liyanhui1228 @c24t @mayurkale22 too |
I haven't seen this for a while, not sure if still a problem. My PR #291 was unrelated I believe. |
It doesn't look like it's fixed in the auth library, and I don't see any changes in the exporter or transport that would have fixed this since you opened the ticket. That said, I haven't run into this issue yet using app default credentials in e.g. the demo app. If you have steps to reproduce it or a full stack trace we can try restarting the background thread on known errors like this, but it may be worth trying to fix the issue in the auth library instead. |
Not reproducible - see previous comments. |
I noticed that currently, if we're using the application default credentials, the
StackdriverExporter
ends up crashing because of this issue ingoogle-auth-library-python
and the only way to make it work again is to restart the background thread.The tracing collection goes fine for a while, and then starts failing in loops with:
The text was updated successfully, but these errors were encountered: