[roll] Roll fuchsia [sestarnix] Avoid iterating over type IDs

We had been iterating over the (sometimes long) extensible bitmaps
specifying types (and transforming the integers they represented, and
gathering them into a HashSet) just to make a membership query. We can
do the same membership query with a view over the underlying
ExtensibleBitmap.

(We could do the same for user IDs and role IDs, but we don't at this
time have any performance data indicating that that would measurably
improve any of our current executions.)

(We still iterate over and collect the integers in the error-handling
path, but that doesn't have performance implications.)

Original-Fixes: 458317188
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1428734
Original-Revision: 547e5e9022470c3ed3fe92daa916941dce53a4c2
GitOrigin-RevId: a10f18a39e3ebc520f653f40e274b830ee8eecb2
Change-Id: I3dba626150c6ebc6d3494fafc23589e221737f11
1 file changed
tree: f37838aef6b763c0dd0b8c7bfae56fa79c8f7c90
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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.