-
Notifications
You must be signed in to change notification settings - Fork 640
Retry GoogleDataTransport Connection Errors #1705
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
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary Size ReportAffected SDKs
Test Logs
NotesHead commit (94d853c7) is created by Prow via merging commits: 037282f e2af542. |
In cases where there is bad connection, the current behavior deletes the cached reports because they are caught as an
IOException
. They appear to be encoding errors, when in reality it's an error opening theOutputStream
that is the connection.This changes it so that when the
IOException
is due to connection problems, we retry the upload instead of deleting it.This is where we transform status numbers into success, fatal, and transient errors: CctTransportBackend.java
This is where we decide to delete fatal errors, and retry transient errors: Uploader.java