- Sort Score
- Result 10 results
- Languages All
Results 1 - 8 of 8 for Monday (0.39 sec)
-
src/test/java/org/codelibs/fess/helper/IntervalControlHelperTest.java
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
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 10 13:41:04 UTC 2025 - 13.1K bytes - Viewed (0) -
src/main/java/org/codelibs/fess/helper/IntervalControlHelper.java
/** * 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) {
Registered: Thu Sep 04 12:52:25 UTC 2025 - Last Modified: Thu Jul 17 08:28:31 UTC 2025 - 9.9K bytes - Viewed (0) -
guava/src/com/google/common/collect/ComparisonChain.java
* 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
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Mon Mar 17 20:26:29 UTC 2025 - 11.1K bytes - Viewed (0) -
guava/src/com/google/common/reflect/Types.java
* 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
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Sep 03 14:03:14 UTC 2025 - 23.5K bytes - Viewed (0) -
android/guava/src/com/google/common/reflect/Types.java
* 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
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Wed Sep 03 14:03:14 UTC 2025 - 23.6K bytes - Viewed (0) -
android/guava/src/com/google/common/hash/BloomFilter.java
* 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
Registered: Fri Sep 05 12:43:10 UTC 2025 - Last Modified: Sun Aug 31 13:15:26 UTC 2025 - 26.9K bytes - Viewed (0) -
CHANGELOG.md
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.
Registered: Fri Sep 05 11:42:10 UTC 2025 - Last Modified: Mon Jul 07 19:32:33 UTC 2025 - 31.6K bytes - Viewed (1) -
CHANGELOG/CHANGELOG-1.2.md
* --etcd-cafile (if not using system roots) * As part of preparation in 1.2 for adding support for protocol buffers (and the direct YAML support in the API available today), the Content-Type and Accept headers are now properly handled as per the HTTP spec. As a consequence, if you had a client that was sending an invalid Content-Type or Accept header to
Registered: Fri Sep 05 09:05:11 UTC 2025 - Last Modified: Fri Dec 04 06:36:19 UTC 2020 - 41.4K bytes - Viewed (0)