Google Git
Sign in
chromium / codesearch / chromium / src / refs/tags/122.0.6261.86
commitc911bece0c850615349b2f3fb1d694320f575507[log] [tgz]
authorAlexander Bolodurin <alexbn@chromium.org>Fri Feb 23 23:52:59 2024
committerChromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>Fri Feb 23 23:52:59 2024
tree3d8b88a9cc9d2dc1244830183b51a96bb1adce3b
parent3f0b92e816fb9fe747d07d8ff9b890514ec2dd54 [diff]
[office] serialise uploads

Every upload handler creates a separate CopyOrMoveIOTask for each file,
which does its own conflict resolution. This may result in tasks
resolving to the same destination file, and multiple source files being
copied to the same destination, losing one of the files.

In the long run we should have a single CopyOrMoveIOTask here, but
serialising uploads is the least invasive change at this point.

(cherry picked from commit 3facb0fec956f69dc41be1c73fc0028ec41b18c1)

Bug: b/325356207
Change-Id: Ie5af1f0da346ef913fe8fa004418fb34c84a9139
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5302359
Commit-Queue: Alexander Bolodurin <alexbn@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1261480}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5305837
Reviewed-by: Josh Simmons <simmonsjosh@google.com>
Cr-Commit-Position: refs/branch-heads/6261@{#938}
Cr-Branched-From: 9755d9d81e4a8cb5b4f76b23b761457479dbb06b-refs/heads/main@{#1250580}
2 files changed
tree: 3d8b88a9cc9d2dc1244830183b51a96bb1adce3b
  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. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. webkit/
  51. clank
  52. internal
  53. ios_internal
  54. native_client
  55. signing_keys
  56. v8
  57. .clang-format
  58. .clang-tidy
  59. .clangd
  60. .eslintrc.js
  61. .git-blame-ignore-revs
  62. .gitallowed
  63. .gitattributes
  64. .gitignore
  65. .gitmodules
  66. .gn
  67. .mailmap
  68. .rustfmt.toml
  69. .vpython3
  70. .yapfignore
  71. ATL_OWNERS
  72. AUTHORS
  73. BUILD.gn
  74. CODE_OF_CONDUCT.md
  75. codereview.settings
  76. DEPS
  77. DIR_METADATA
  78. LICENSE
  79. LICENSE.chromium_os
  80. OWNERS
  81. PRESUBMIT.py
  82. PRESUBMIT_test.py
  83. PRESUBMIT_test_mocks.py
  84. README.md
  85. 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.