Google Git
Sign in
chromium / chromium / src / 393b6a4c87aee5208a422e559089e873ec36cf54
commit393b6a4c87aee5208a422e559089e873ec36cf54[log] [tgz]
authorArthur Milchior <arthurmilchior@chromium.org>Thu Jan 30 14:07:27 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Thu Jan 30 14:07:27 2025
tree6d67b47ffc22286f2dc1a79018eb75225b187f82
parentebbcf748030d5e95faf5b364d1cd669a84f5cc30 [diff]
[iOS][Account]Retry fetching hosted domain with exponential backoff

The Assigner now has an array of identities it must fetch. It uses
the same exponential backoff for all identities, resetting it in case of
success.

It’s not clear what would be the ideal parameters. The policy can
easily be changed without touching of the remaining of the code.
Currently, the decision is:
* to stop only if there are at least five consecutive failures,
(that is, probably some issue to connect to Gaia)
* tries all identities requested at least twice.

In case of repeated fetch failure, current implementation still assign
the identities to the default profile. Deciding what to actually do
in case of repeated failure is outside the scope of this CL.

Bug: 385133710, 331783685
Change-Id: Iad969403978ae181ca710180b90551073c829a54
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6200610
Auto-Submit: Arthur Milchior <arthurmilchior@chromium.org>
Reviewed-by: Marc Treib <treib@chromium.org>
Commit-Queue: Arthur Milchior <arthurmilchior@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1413453}
1 file changed
tree: 6d67b47ffc22286f2dc1a79018eb75225b187f82
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. codelabs/
  13. components/
  14. content/
  15. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. clank
  50. internal
  51. ios_internal
  52. native_client
  53. signing_keys
  54. v8
  55. .clang-format
  56. .clang-tidy
  57. .clangd
  58. .git-blame-ignore-revs
  59. .gitallowed
  60. .gitattributes
  61. .gitignore
  62. .gitmodules
  63. .gn
  64. .mailmap
  65. .rustfmt.toml
  66. .vpython3
  67. .yapfignore
  68. ATL_OWNERS
  69. AUTHORS
  70. BUILD.gn
  71. CODE_OF_CONDUCT.md
  72. codereview.settings
  73. CPPLINT.cfg
  74. CRYPTO_OWNERS
  75. DEPS
  76. DIR_METADATA
  77. LICENSE
  78. LICENSE.chromium_os
  79. OWNERS
  80. PRESUBMIT.py
  81. PRESUBMIT_test.py
  82. PRESUBMIT_test_mocks.py
  83. README.md
  84. WATCHLISTS
README.md

Logo Chromium

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.