[roll] Roll fuchsia [fxfs] Refactor how next_key works

next_key was a big source of confusion.  This simplifies next_key
considerably.  To achieve the same functionality we use overlaps instead
to determine whether a key we have found overlaps the search key.

This also adds some assertions to ensure that FullRange queries are
always using search keys.

Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1618423
Original-Original-Revision: 407803b9c4b35a8eb316e5514d368f5827861900
GitOrigin-RevId: 6158d2f5455f262158a2ed3041aeed221a6bab5a
Change-Id: Ib0e01ac9bb9e76084008199796c336086b1f85eb
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1618469
Cr-Commit-Position: refs/heads/main@{#193093}
1 file changed
tree: 7e40d07c6e24e155f1c47555b6f69f3ba02f2f20
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance in one of the communication channels documented at get involved.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.