Google Git
Sign in
chromium / chromium / src / 3591a93c6c0d4cbe50fa8f17c844346e6029d3d5
commit3591a93c6c0d4cbe50fa8f17c844346e6029d3d5[log] [tgz]
authorRushan Suleymanov <rushans@google.com>Wed Apr 23 05:26:12 2025
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Apr 23 05:26:12 2025
treeff639a478f86bab772ba9feb5aed057b5f3f01f5
parentffd7e207790bf8c42ad7d69d4c453bd7d8651ac4 [diff]
[Sync] Use GaiaId instead of CoreAccountId in activation request

CoreAccountId currently contains Gaia ID, hence the migration should be
nearly no-op on most clients. Few clients which did not complete the
migration to Gaia ID should not have behavioral changes, because the
serialized value is replaced on browser startup with a new value in sync
metadata.

This migration is needed to avoid CoreAccountId serialization because it
may change over time, while GaiaId is more stable.

In this CL in some data type tests (e.g. ReadingList) the new GaiaId is
compared against CoreAccountId. This will be changed in follow-up CLs
where their models will return GaiaId instead.

Bug: 383089506
Change-Id: Ica4321eae4d765861153f4d8149d540154cb38d4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6468934
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Mikel Astiz <mastiz@chromium.org>
Commit-Queue: Rushan Suleymanov <rushans@google.com>
Cr-Commit-Position: refs/heads/main@{#1450390}
20 files changed
tree: ff639a478f86bab772ba9feb5aed057b5f3f01f5
  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.