* another implementation but also forces AbstractFutureState to be able to do the
         * same—hence the try-catch here.
         *
         * (Really, we're fortunate that breaking AtomicReferenceFieldUpdater doesn't break _even
         * more_ things.)
         */
        helper = new SynchronizedHelper();
      }
    }
    ATOMIC_HELPER = helper;

  }

  @Test
  fun authenticate() {
    server.enqueue(
      MockResponse(
        code = HttpURLConnection.HTTP_UNAUTHORIZED,
        headers = headersOf("www-authenticate", "Basic realm=\"protected area\""),
        body = "Please authenticate.",
      ),
    )
    server.enqueue(
      MockResponse(body = "Successful auth!"),
    )
    val credential = basic("username", "password")

    - [Server binaries](#server-binaries-7)
    - [Node binaries](#node-binaries-7)
  - [Changelog since v1.17.8](#changelog-since-v1178)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-8)
    - [Bug or Regression](#bug-or-regression-7)
  - [Dependencies](#dependencies-8)
    - [Added](#added-8)

    if (expected.equals(in)) {
      assertThat(out).isSameInstanceAs(in);
    } else {
      assertThat(out).isEqualTo(expected);
    }
  }

  // Test collapse() a little differently than the rest, as we really want to
  // cover lots of different configurations of input text
  public void testCollapse() {
    // collapsing groups of '-' into '_' or '-'
    doTestCollapse("-", "_");
    doTestCollapse("x-", "x_");

   * tests that assert that a certain amount of time has passed, that the method returned `false`,
   * or even that an interrupt occurred (if the spurious wakeup happens before the interrupt).
   *
   * Fundamentally, there's not really anything we can do about that. In the unlikely event that it
   * comes up in practice (maybe through some kind of sanitizer-like testing that intentionally

        Lists.newArrayList(FluentIterable.from(ImmutableList.of(1, 2, 3, 4))));
  }

  @SuppressWarnings({
    "deprecation", // test of deprecated method
    // We need to test that from(FluentIterable) really is just a null check.
    "InlineMeInliner",
  })
  public void testFrom_alreadyFluentIterable() {
    FluentIterable<Integer> iterable = FluentIterable.from(asList(1));

    - [Avoiding Collisions in IP allocation to Services](#avoiding-collisions-in-ip-allocation-to-services)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-17)
    - [Deprecation](#deprecation)
    - [API Change](#api-change-4)
    - [Feature](#feature-15)

     *     <li>"snapshot" - query only snapshot repositories to discover versions</li>
     * </ul>
     * Default (when unset) is using request carried nature. Hence, this configuration really makes sense with value
     * {@code "auto"}, while ideally callers needs update and use newly added method on version range request to
     * express preference.
     *
     * @since 4.0.0
     */

    - [Summary API in kubelet doesn't have accelerator metrics](#summary-api-in-kubelet-doesnt-have-accelerator-metrics)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)
  - [Changes by Kind](#changes-by-kind-14)
    - [Deprecation](#deprecation)
    - [API Change](#api-change-4)
    - [Feature](#feature-6)

   * going through {@code FluentIterable} at all), the more performant and idiomatic your code will
   * be. This method is a transitional aid, to be used only when really necessary.
   *
   * @since 21.0
   */
  public final Stream<E> stream() {
    return Streams.stream(getDelegate());
  }