*
     * @param responseKeyNT the NT response key
     * @param serverChallenge the server challenge bytes
     * @param clientChallenge the client challenge bytes
     * @param nanos1601 the timestamp in nanoseconds since 1601
     * @param targetInfo the target information from the Type 2 message
     * @return the NTLMv2 response bytes
     */

  public final FluentFuture<V> withTimeout(
      Duration timeout, ScheduledExecutorService scheduledExecutor) {
    return withTimeout(toNanosSaturated(timeout), TimeUnit.NANOSECONDS, scheduledExecutor);
  }

  /**
   * Returns a future that delegates to this future but will finish early (via a {@link
   * TimeoutException} wrapped in an {@link ExecutionException}) if the specified timeout expires.

server).

If you are coming from another async framework that does not work in the way described above and you are used to defining trivial compute-only *path operation functions* with plain `def` for a tiny performance gain (about 100 nanoseconds), please note that in **FastAPI** the effect would be quite opposite. In these cases, it's better to use `async def` unless your *path operation functions* use code that performs blocking <abbr title="Input/Output: disk reading or writing, network...

        bodySource.readByte()
      }.also { expected ->
        // Timed out as expected.
        val elapsedNanos = System.nanoTime() - startNanos
        val elapsedMillis = TimeUnit.NANOSECONDS.toMillis(elapsedNanos)
        assertThat(elapsedMillis).isLessThan(500)
      }
    }
  }

  /** https://github.com/square/okhttp/issues/442  */
  @Test
  fun tlsTimeoutsNotRetried() {

- Upgrade Stackdriver Logging Agent addon image to 0.6-1.6.0-1 to use Fluentd v1.2. This provides nanoseconds timestamp granularity for logs. ([#70954](https://github.com/kubernetes/kubernetes/pull/70954), [@qingling128](https://github.com/qingling128))

    val connection1 = getResponse(newRequest("/"))
    val inputStream = connection1.body.byteStream()
    inputStream.close()
    val elapsedNanos = System.nanoTime() - startNanos
    val elapsedMillis = TimeUnit.NANOSECONDS.toMillis(elapsedNanos)

    // If we're working correctly, this should be greater than 100ms, but less than double that.
    // Previously we had a bug where we would download the entire response body as long as no

        this.flags = SMBUtil.readInt4(buffer, bufferIndex + 4); // Flags (4 bytes)
        return 8;
    }

    /**
     * Get the timeout value in 100-nanosecond intervals (raw wire format)
     * @return the timeout in 100-nanosecond intervals
     */
    public long getTimeout100Ns() {
        return timeout100Ns;
    }

    /**
     * Get the timeout value converted to milliseconds

        return timeoutMs;
    }

    /**
     * Get the timeout value in 100-nanosecond intervals as required by MS-SMB2
     * @return the timeout in 100-nanosecond intervals
     */
    public long getTimeoutFor100Ns() {
        if (timeoutMs == 0) {
            return 0L; // Persistent handles use 0
        }
        // Convert milliseconds to 100-nanosecond intervals
        // 1 ms = 10,000 * 100ns intervals

        long lastAccess = 1600000100000L;
        long lastWrite = 1600000200000L;
        long change = 1600000300000L;
        int attributes = 0x1234;
        // Convert Unix time to Windows FILETIME (100-nanosecond intervals since 1601)
        long MILLISECONDS_BETWEEN_1970_AND_1601 = 11644473600000L;
        writeLong(buffer, 0, (create + MILLISECONDS_BETWEEN_1970_AND_1601) * 10000L);

        // Decode output parameters for WitnessHeartbeat

        // Response sequence number (64-bit)
        responseSequenceNumber = buf.dec_ndr_hyper();

        // Heartbeat interval (64-bit, in 100-nanosecond intervals)
        // Convert from FILETIME intervals to milliseconds
        long filetimeInterval = buf.dec_ndr_hyper();
        heartbeatInterval = filetimeInterval / 10000; // Convert to milliseconds
    }