Roll nearby-connections from beb67fc02a5b to 384d144d6e16 (2 revisions) https://chromium.googlesource.com/external/github.com/google/nearby-connections.git/+log/beb67fc02a5b..384d144d6e16 2022-11-15 jsobczak@google.com Do not use absl::string_view as keys. > absl::string_view usually is not suitable type for a member variable nor a map key. > The string referenced by string_view may run out of scope. > PiperOrigin-RevId: 488743930 > 2022-11-15 jsobczak@google.com Do not use an iterator after modifying a collection > Iterators returned by equals_range() are no longer valid when collection is modified. > > PiperOrigin-RevId: 488728730 > If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://skia-autoroll.corp.goog/r/nearby-connections-chromium Please CC chromeos-cross-device-eng+autoroll@google.com,jonfan@google.com,nearby-chromeos-eng+autoroll@google.com on the revert to ensure that a human is aware of the problem. To file a bug in Chromium: https://bugs.chromium.org/p/chromium/issues/entry To report a problem with the AutoRoller itself, please file a bug: https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Cq-Include-Trybots: luci.chrome.try:linux-nearby-chrome-fyi Bug: None Tbr: chromeos-cross-device-eng+autoroll@google.com,jonfan@google.com,nearby-chromeos-eng+autoroll@google.com Change-Id: Ie8b159935146e0d0befef85fa531bb538d7286cf Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4026319 Commit-Queue: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Bot-Commit: chromium-internal-autoroll <chromium-internal-autoroll@skia-corp.google.com.iam.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1071944}
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.