Roll nearby-connections from f788b891908d to 35a8289ef40b (23 revisions)

https://chromium.googlesource.com/external/github.com/google/nearby-connections.git/+log/f788b891908d..35a8289ef40b

2024-04-16 eidenkim@google.com Block any BWU frames before the NC connection accepted by both side
> PiperOrigin-RevId: 625459811
>

2024-04-16 hais@google.com Automated Code Change
> PiperOrigin-RevId: 625233447
>

2024-04-15 ftsui@google.com Add experiment_log.proto
> PiperOrigin-RevId: 625106788
>

2024-04-15 ftsui@google.com Change ownership model of NearbySharingEventLogger.
> PiperOrigin-RevId: 625064926
>

2024-04-15 eidenkim@google.com Add a flag to nearby_connections_feature_flags.h manually
> PiperOrigin-RevId: 625010913
>

2024-04-15 ftsui@google.com Create common MockEventLogger.
> PiperOrigin-RevId: 624994414
>

2024-04-15 eidenkim@google.com Add flags to nearby_sharing_feature_flags.h manually
> PiperOrigin-RevId: 624970993
>

2024-04-13 hais@google.com Automated Code Change
> PiperOrigin-RevId: 624435924
>

2024-04-12 hais@google.com Initial implementation of rust decoder
> PiperOrigin-RevId: 624312324
>

2024-04-12 dclasson@google.com [Nearby Connections] Rename async scanning flag
> Renames the enable_ble_v2_async_scanning_advertising flag to just
> enable_ble_v2_async_scanning, reflecting that scanning/advertising
> can be enabled independently. Work required to add async
> advertising is tracked in b/333408829.
>
> PiperOrigin-RevId: 624254277
>

2024-04-12 hais@google.com annotate EventType enum
> PiperOrigin-RevId: 624254082
>

2024-04-11 ftsui@google.com Fix TSAN errors.
> PiperOrigin-RevId: 623943443
>

2024-04-11 ftsui@google.com Fix TSAN error.
> PiperOrigin-RevId: 623926109
>

2024-04-11 ftsui@google.com TSAN error fixes.
> PiperOrigin-RevId: 623908987
>

2024-04-11 awadhera@google.com Update Android README to expose more of the QS surfaces
> PiperOrigin-RevId: 623883363
>

2024-04-11 hais@google.com Update Westworld logging to include connection events
> PiperOrigin-RevId: 623881505
>

2024-04-11 hais@google.com Automated Code Change
> PiperOrigin-RevId: 623732541
>

2024-04-11 hais@google.com Deprecate the IO_ENDPOINT_IO_ERROR_ON_XXX related result code due to we changed to apply the CONNECTIVITY_CHANNEL_IO_ERROR_ON_XXX in cl/621498234,
> PiperOrigin-RevId: 623718959
>

2024-04-11 edwinwu@google.com Add the privacy manifests for swift NC-SDK.
> PiperOrigin-RevId: 623676227
>

2024-04-10 awadhera@google.com Merge pull request #2421 from anayw2001/main
> Update Android documentation

2024-04-10 hais@google.com Multiplex implementation - Create Virtual Output Stream
> PiperOrigin-RevId: 623540454
>

2024-04-10 bourdakos1@gmail.com PR #2404: Add license header to all source files
> Imported from GitHub PR https://github.com/google/nearby/pull/2404
>
> Copybara import of the project:
>
> --
> a6fbb3c396321c0b9012b787323f5f2ff652fd8f by Nick Bourdakos <bourdakos1@gmail.com>:
>
> Add license header to all source files
>
> Merging this change closes #2404
>
> PiperOrigin-RevId: 623540004
>

2024-04-10 hais@google.com Automated Code Change
> PiperOrigin-RevId: 623376075
>

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,kyleshima@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://issues.skia.org/issues/new?component=1389291&template=1850622

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,kyleshima@google.com,nearby-chromeos-eng+autoroll@google.com
Change-Id: I75ed7c29669fe7c79ebd74f15b3d4f2ccb5b592d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5458848
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@{#1288428}
3 files changed
tree: fd6ba189dca055f1d4f96e556cde7ba904b35dab
  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. .clang-format
  52. .clang-tidy
  53. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. 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.