ash: Report internal errors when fetching calendar events CalendarEventFetch now also requires a callback for handling "internal" errors, i.e. any errors that didn't come from the Calendar API. As with the FetchCompleteCallback we supply, CalendarModel's FetchInternalErrorCallback destroys the CalendarEventFetch object that invoked it. Add a timer for each calendar event fetch, to fire if we go too long without receiving a response from the Calendar API. In this case we report an internal error of TIMEOUT. Bug: 1298187 Change-Id: I94e5a0a48f787bf00279068fd4a8f14cc95db460 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3472463 Reviewed-by: Alex Newcomer <newcomer@chromium.org> Reviewed-by: Jiaming Cheng <jiamingc@chromium.org> Reviewed-by: Zentaro Kavanagh <zentaro@chromium.org> Commit-Queue: Roger Tinkoff <rtinkoff@google.com> Cr-Commit-Position: refs/heads/main@{#972768}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.