The source could not be displayed because it is larger than 1 MB.
You can
load it anyway or download it
instead.
-
Mikel Astiz authored
When interacting with the sync server, HTTP errors that represent auth errors (401) get treated as SyncerError::SYNC_AUTH_ERROR. When reporting these cases in metric like Sync.SharingMessage.CommitResult, they should not contribute as "Sync server error", since the nature of the problem is different and very likely transient (i.e. expired tokens). In follow-up patches, the actual logic to handle this situation should be improved. Bug: 1097054 Change-Id: I2e806fab89a49e8840324f98d68f1aadd1c40080 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2253845 Commit-Queue: Mikel Astiz <mastiz@chromium.org> Reviewed-by:
Rushan Suleymanov <rushans@google.com> Reviewed-by:
Alex Chau <alexchau@chromium.org> Cr-Commit-Position: refs/heads/master@{#780273}
9d10067b