</p>
    <p>
      Execution traces now use the operating system's clock on most platforms (Windows excluded) so
      it is possible to correlate them with traces produced by lower-level components.
      Execution traces no longer depend on the reliability of the platform's clock to produce a correct trace.
      Execution traces are now partitioned regularly on-the-fly and as a result may be processed in a

    on up-to-date Kotlin releases (1.6.21) but no longer needs that version as a runtime dependency.
    This should make it easier to use OkHttp in Gradle plugins.

 *  Fix: Don't start the clock on response timeouts until the request body is fully transmitted.
    This is only relevant for duplex request bodies, because they are written concurrently when
    reading the response body.

pkg syscall (freebsd-arm64), const LOCK_EX = 2
pkg syscall (freebsd-arm64), const LOCK_EX ideal-int
pkg syscall (freebsd-arm64), const LOCK_NB = 4
pkg syscall (freebsd-arm64), const LOCK_NB ideal-int
pkg syscall (freebsd-arm64), const LOCK_SH = 1
pkg syscall (freebsd-arm64), const LOCK_SH ideal-int
pkg syscall (freebsd-arm64), const LOCK_UN = 8
pkg syscall (freebsd-arm64), const LOCK_UN ideal-int

beating.  Now, if you only kept on good terms with him, he'd do
almost anything you liked with the clock.  For instance, suppose
it were nine o'clock in the morning, just time to begin lessons:
you'd only have to whisper a hint to Time, and round goes the
clock in a twinkling!  Half-past one, time for dinner!'

  (`I only wish it was,' the March Hare said to itself in a
whisper.)

pkg syscall (freebsd-386), const SYS_CHROOT = 61
pkg syscall (freebsd-386), const SYS_CLOCK_GETCPUCLOCKID2 = 247
pkg syscall (freebsd-386), const SYS_CLOCK_GETCPUCLOCKID2 ideal-int
pkg syscall (freebsd-386), const SYS_CLOCK_GETRES = 234
pkg syscall (freebsd-386), const SYS_CLOCK_GETTIME = 232
pkg syscall (freebsd-386), const SYS_CLOCK_SETTIME = 233
pkg syscall (freebsd-386), const SYS_CLOSE = 6

pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETCPUCLOCKID2 = 247 #53466
pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETCPUCLOCKID2 ideal-int #53466
pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETRES = 234 #53466
pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETRES ideal-int #53466
pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETTIME = 232 #53466
pkg syscall (freebsd-riscv64), const SYS_CLOCK_GETTIME ideal-int #53466

beating.  Now, if you only kept on good terms with him, he'd do
almost anything you liked with the clock.  For instance, suppose
it were nine o'clock in the morning, just time to begin lessons:
you'd only have to whisper a hint to Time, and round goes the
clock in a twinkling!  Half-past one, time for dinner!'

  (`I only wish it was,' the March Hare said to itself in a
whisper.)

      .isEqualTo(lastModifiedDate)
  }

  @Test
  fun maxAgeInThePastWithDateHeaderButNoLastModifiedHeader() {
    // Chrome interprets max-age relative to the local clock. Both our cache
    // and Firefox both use the earlier of the local and server's clock.
    assertNotCached(
      MockResponse.Builder()
        .addHeader("Date: " + formatDate(-120, TimeUnit.SECONDS))
        .addHeader("Cache-Control: max-age=60")

     * <p>
     * Wildcard expressions will not filter workgroup names or server names.
     *
     * <blockquote>
     * 
     * <pre>
     * winnt&gt; ls c?o*
     * clock.avi                  -rw--      82944 Mon Oct 14 1996 1:38 AM
     * Cookies                    drw--          0 Fri Nov 13 1998 9:42 PM
     * 2 items in 5ms
     * </pre>
     * 
     * </blockquote>
     * 

pkg syscall (netbsd-arm64), const LOCK_EX = 2
pkg syscall (netbsd-arm64), const LOCK_EX ideal-int
pkg syscall (netbsd-arm64), const LOCK_NB = 4
pkg syscall (netbsd-arm64), const LOCK_NB ideal-int
pkg syscall (netbsd-arm64), const LOCK_SH = 1
pkg syscall (netbsd-arm64), const LOCK_SH ideal-int
pkg syscall (netbsd-arm64), const LOCK_UN = 8
pkg syscall (netbsd-arm64), const LOCK_UN ideal-int