assertTrue(rule.isTarget(23, 30, 1)); // 23:30 on Sunday
        assertTrue(rule.isTarget(22, 0, 1)); // 22:00 on Sunday (start time)

        // Within range (next day)
        assertTrue(rule.isTarget(1, 30, 1)); // 1:30 on Sunday (actually Monday morning)
        assertTrue(rule.isTarget(2, 0, 1)); // 2:00 on Sunday (actually Monday morning)

        // Outside range

    /**
     * Adds a new interval rule to the rule list.
     *
     * @param from the start time in HH:MM format
     * @param to the end time in HH:MM format
     * @param days comma-separated list of days (1=Sunday, 7=Saturday)
     * @param delay the delay in milliseconds to apply during this interval
     */
    public void addIntervalRule(final String from, final String to, final String days, final long delay) {

     *
     * @param days the number of days to look back from the current time
     */
    public void deleteBefore(final int days) {
        final long oneday = 24 * 60 * 60 * 1000L;
        final long targetTime = ComponentUtil.getSystemHelper().getCurrentTimeAsLong() - days * oneday;
        jobLogBhv.queryDelete(cb -> {
            cb.query().setEndTime_LessThan(targetTime);
        });
    }

    /**

   * we wanted to support legacy classes that implement the raw type {@code Comparable} (instead of
   * implementing {@code Comparable<Foo>}) without producing warnings. If so, we would prefer today
   * to produce warnings in that case, and we may change this method to do so in the future. Support
   * for raw {@code Comparable} types in Guava in general is tracked as <a

   * AnnotatedElement}, which {@code TypeVariable} began to extend only in Java 8. Those methods
   * refer only to types present under Android, so we could implement them in {@code
   * TypeVariableImpl} today. (We could probably then make {@code TypeVariableImpl} implement {@code
   * AnnotatedElement} so that we get partial compile-time checking.)
   *
   * <p>This workaround should be removed at a distant future time when <a

   * AnnotatedElement}, which {@code TypeVariable} began to extend only in Java 8. Those methods
   * refer only to types present under Android, so we could implement them in {@code
   * TypeVariableImpl} today. (We could probably then make {@code TypeVariableImpl} implement {@code
   * AnnotatedElement} so that we get partial compile-time checking.)
   *
   * <p>This workaround should be removed at a distant future time when <a

jls-sto1.elastx.net
jls-sto2.elastx.net
jls-sto3.elastx.net
jmp
jnj
jo
joboji.iwate.jp
jobs
joburg
joetsu.niigata.jp
jogasz.hu
johana.toyama.jp
joinville.br
jolster.no
jondal.no
jor.br
jorpeland.no
joso.ibaraki.jp
jot
jotelulu.cloud
journal.aero
journalist.aero
jouwweb.site
joy
joyo.kyoto.jp
jozi.biz
jp
jp.eu.org
jp.net

        body = "I'm not even supposed to be here today.",
      ),
    )
    executeSynchronously("/")
      .assertFailure("HTTP 204 had non-zero Content-Length: 39")
  }

  @Test
  fun http205WithBodyDisallowed() {
    server.enqueue(
      MockResponse(
        code = 205,
        body = "I'm not even supposed to be here today.",
      ),
    )
    executeSynchronously("/")

 * supported by future versions of this library. However, serial forms generated by newer versions
 * of the code may not be readable by older versions of the code (e.g., a serialized Bloom filter
 * generated today may <i>not</i> be readable by a binary that was compiled 6 months ago).
 *
 * <p>As of Guava 23.0, this class is thread-safe and lock-free. It internally uses atomics and

    prepared to build a TLS API for Kotlin/Native.

    We'd prefer a multiplatform HTTP client API that's backed by OkHttp on Android and JVM, and
    other engines on other platforms. [Ktor] does this pretty well today!

 *  Breaking: Use `kotlin.time.Duration` in APIs like `OkHttpClient.Builder.callTimeout()`. This
    update also drops support for the `DurationUnit` functions introduced in earlier alpha releases
    of OkHttp 5.