Function<? super Throwable, ? extends V> fallback,
      Executor executor) {
    return AbstractCatchingFuture.create(input, exceptionType, fallback, executor);
  }

  public static <V extends @Nullable Object> ListenableFuture<V> catchingAsync(
      ListenableFuture<? extends V> input,
      Class<Throwable> exceptionType,
      AsyncFunction<? super Throwable, ? extends V> fallback,
      Executor executor) {

     * Execute a callable through the circuit breaker with fallback
     *
     * @param <T> return type
     * @param callable the callable to execute
     * @param fallback fallback supplier if circuit is open
     * @return the result or fallback value
     * @throws Exception if execution fails and no fallback provided
     */
    public <T> T call(Callable<T> callable, Callable<T> fallback) throws Exception {

     * potential NTLM fallback (if the server does not support kerberos).
     *
     * @param subject
     *            represents the user who perform Kerberos authentication. Should at least contain a TGT for the user.
     * @param domain
     *            domain for NTLM fallback
     * @param username
     *            user for NTLM fallback
     * @param password

    }

    /**
     * Creates a fallback search intent when intent detection fails.
     *
     * @param originalMessage the original user message
     * @return the fallback search intent result
     */
    public static IntentDetectionResult fallbackSearch(final String originalMessage) {
        return new IntentDetectionResult(ChatIntent.SEARCH, originalMessage, null, "Fallback: using original message as query");
    }

### [Fast Fallback](https://square.github.io/okhttp/5.x/okhttp/okhttp3/-ok-http-client/-builder/fast-fallback)

Since version 5.0, `OkHttpClient` supports fast fallback, which is our implementation of Happy Eyeballs [RFC 6555](https://datatracker.ietf.org/doc/html/rfc6555).

 * and performant but introduces some testing difficulties. This test exercises the two fallback
 * strategies.
 *
 * <ul>
 *   <li>SafeAtomicHelper: uses Atomic FieldsUpdaters to implement synchronization
 *   <li>SynchronizedHelper: uses {@code synchronized} blocks for synchronization
 * </ul>
 *
 * To force selection of our fallback strategies we load {@link AggregateFutureState} (and all of

import java.util.EnumSet;
import java.util.Set;

/**
 * Interface for RDMA provider implementations.
 *
 * This interface abstracts different RDMA implementations such as
 * InfiniBand, iWARP, RoCE, or TCP fallback providers.
 */
public interface RdmaProvider {

    /**
     * Check if RDMA is available on this system
     *
     * @return true if RDMA can be used, false otherwise
     */
    boolean isAvailable();

 *
 * @author Kevin Damm
 * @author Kyle Maddison
 */
final class LittleEndianByteArray {

  /**
   * The instance that actually does the work; delegates to VarHandle, Unsafe, or a Java-8
   * compatible pure-Java fallback.
   */
  private static final LittleEndianBytes byteArray = makeGetter();

  /**
   * Load 8 bytes into long in a little endian manner, from the substring between position and

import okio.BufferedSource

/**
 * [HTTP/2][Protocol.HTTP_2] only. Processes server-initiated HTTP requests on the client.
 * Implementations must quickly dispatch callbacks to avoid creating a bottleneck.
 *
 * While [onReset] may occur at any time, the following callbacks are expected in order,
 * correlated by stream ID.
 *
 *  * [onRequest]
 *  * [onHeaders] (unless canceled)
 *  * [onData] (optional sequence of data frames)
 *

        assertTrue(ex.getMessage().contains("Cannot use netbios/short names"));
    }

    @Test
    @DisplayName("createContext: no Kerberos in initial token and no fallback -> throws")
    void createContext_noKerberosNoFallback_throws() throws CIFSException {
        Kerb5Authenticator auth = new Kerb5Authenticator((Subject) null);