* Permitted to retry and make multiple calls to `Chain.proceed()`.
 * Can adjust Call timeouts using withConnectTimeout, withReadTimeout, withWriteTimeout.

**Network Interceptors**

 * Able to operate on intermediate responses like redirects and retries.
 * Not invoked for cached responses that short-circuit the network.
 * Observe the data just as it will be transmitted over the network.

   * apply to {@code getAnnotatedBounds()}. This does mean that users on Java who obtain an instance
   * of {@code TypeVariable} from {@link TypeResolver#resolveType} will not be able to call {@code
   * getAnnotatedBounds()} on it, but that should hopefully be rare.
   *
   * <p>TODO: b/147144588 - We are currently also missing the methods inherited from {@link

 * explanation.
 *
 * @param <K> the most general key type this builder will be able to create caches for. This is
 *     normally {@code Object} unless it is constrained by using a method like {@link
 *     #removalListener}. Cache keys may not be null.
 * @param <V> the most general value type this builder will be able to create caches for. This is
 *     normally {@code Object} unless it is constrained by using a method like {@link

            assertEquals(EncryptionNegotiateContext.NEGO_CTX_ENC_TYPE, encContext.getContextType());
        }

        @Test
        @DisplayName("Should be able to use polymorphically")
        void testPolymorphicUsage() {
            // Arrange
            NegotiateContextResponse[] contexts =

      this
        .route()
        .address.url.host
    ) {
      return true // This connection is a perfect match.
    }

    // At this point we don't have a hostname match. But we still be able to carry the request if
    // our connection coalescing requirements are met. See also:
    // https://hpbn.co/optimizing-application-delivery/#eliminate-domain-sharding

            //
            // 2. not to cancel any Future the user returned from an AsyncCallable
            //
            // We promise this because, once we cancel that Future, we would no longer be able to
            // tell when any underlying work it is doing is done. Thus, we might start a new task
            // while that underlying work is still running.
            //

            // Allocate again to test pooling
            RdmaMemoryRegion newSendRegion = bufferManager.getSendRegion(4096);
            assertNotNull(newSendRegion, "Should be able to allocate new send region");

            // Release the new region
            bufferManager.releaseSendRegion(newSendRegion);

    return accessibleObject.getAnnotations();
  }

  @Override
  public final Annotation[] getDeclaredAnnotations() {
    return accessibleObject.getDeclaredAnnotations();
  }

  // We ought to be able to implement GenericDeclaration instead its parent AnnotatedElement.
  // That would give us this method declaration. But for some reason, implementing
  // GenericDeclaration leads to weird errors in Android tests:

            assertTrue(resource.exists(), "Resource should exist");
            assertTrue(resource.isFile(), "Should be a file");
            assertTrue(resource.canWrite(), "Should be writable");

            // Should be able to perform file operations
            assertDoesNotThrow(() -> {
                resource.setReadOnly();
                resource.setReadWrite();
                resource.setAttributes(0x20);

        } catch (IOException e) {
            assertTrue(e.getMessage().contains("endpoint is blank"));
        }
    }

    /**
     * Test thread-safety of connect() method.
     * Multiple threads should be able to call connect() concurrently without issues.
     */
    public void test_connect_threadSafety() throws Exception {
        URL url = new URL("storage://mybucket/object.txt");
        Handler handler = new Handler();