Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 10 of 244 for crashes (0.04 sec)

  1. okhttp/src/commonJvmAndroid/kotlin/okhttp3/Interceptor.kt

     *    indicating that the call was canceled. The interceptor's exception is delivered to the current
     *    thread's [uncaught exception handler][Thread.UncaughtExceptionHandler]. By default this
     *    crashes the application on Android and prints a stacktrace on the JVM. (Crash reporting
     *    libraries may customize this behavior.)
     *
     * A good way to signal a failure is with a synthetic HTTP response:
     *
     * ```kotlin
     *   @Throws(IOException::class)
    Registered: Fri Dec 26 11:42:13 UTC 2025
    - Last Modified: Fri Dec 27 13:39:56 UTC 2024
    - 3.5K bytes
    - Viewed (0)
  2. android/guava/src/com/google/common/base/package-info.java

     *   <li>{@link Stopwatch}
     *   <li>{@link Throwables}
     *   <li>{@link Verify}
     * </ul>
     *
     * <h3>The rest</h3>
     *
     * This package also contains some classes with niche use cases (e.g., {@link Utf8} and {@link
     * Defaults}), as well as a number of classes that have been superseded by additions to the JDK.
     */
    @CheckReturnValue
    @NullMarked
    package com.google.common.base;
    
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Sat Dec 21 14:50:24 UTC 2024
    - 1.7K bytes
    - Viewed (0)
  3. fess-crawler/src/test/java/org/codelibs/fess/crawler/extractor/impl/EXTRACTOR_TESTS_README.md

    ---
    
    ### 2. FilenameExtractorEnhancedTest.java
    **Purpose**: Test FilenameExtractor edge cases and new documentation.
    
    **Key Test Areas**:
    - Parameter handling (null, empty, missing)
    - Special character handling
    - Input stream validation (not consumption)
    - Edge cases (long filenames, paths, whitespace)
    
    **Test Count**: 10 tests
    
    **Key Scenarios**:
    - ✅ Valid filename extraction
    Registered: Sat Dec 20 11:21:39 UTC 2025
    - Last Modified: Wed Nov 19 08:55:01 UTC 2025
    - 5.7K bytes
    - Viewed (0)
  4. .github/ISSUE_TEMPLATE/feature_enhancement_request.yaml

            across a similar need in our own work, that's extremely helpful in studying how broadly
            useful the proposed change will be.
    
      - type: textarea
        attributes:
          label: Concrete Use Cases
          description: Please provide use cases that actually came up in the real world.
        validations:
          required: true
    
      - type: checkboxes
        attributes:
          label: Checklist
          options:
            - label: >
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Fri Nov 17 18:47:47 UTC 2023
    - 3.9K bytes
    - Viewed (0)
  5. src/test/java/jcifs/netbios/NbtExceptionTest.java

        }
    
        /**
         * Test the getErrorString method with various error classes and codes to ensure all branches are covered.
         */
        @ParameterizedTest
        @MethodSource("provideErrorClassAndCodeForGetErrorString")
        @DisplayName("getErrorString should return correct messages for all defined error classes and codes")
        void testGetErrorString(int errorClass, int errorCode, String expectedMessage) {
    Registered: Sat Dec 20 13:44:44 UTC 2025
    - Last Modified: Thu Aug 14 05:31:44 UTC 2025
    - 5.9K bytes
    - Viewed (0)
  6. guava/src/com/google/common/base/Function.java

     * appropriate primitive specialization such as {@code ToIntFunction}) instead whenever possible.
     * Otherwise, at least reduce <i>explicit</i> dependencies on this type by using lambda expressions
     * or method references instead of classes, leaving your code easier to migrate in the future.
     *
     * <p>See the Guava User Guide article on <a
     * href="https://github.com/google/guava/wiki/FunctionalExplained">the use of {@code Function}</a>.
     *
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Tue Apr 15 22:14:00 UTC 2025
    - 2.6K bytes
    - Viewed (0)
  7. android/guava-tests/test/com/google/common/net/HostSpecifierTest.java

    /**
     * {@link TestCase} for {@link HostSpecifier}. This is a relatively cursory test, as HostSpecifier
     * is a thin wrapper around {@link InetAddresses} and {@link InternetDomainName}; the unit tests for
     * those classes explore numerous corner cases. The intent here is to confirm that everything is
     * wired up properly.
     *
     * @author Craig Berry
     */
    @NullUnmarked
    public final class HostSpecifierTest extends TestCase {
    
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Tue May 13 18:46:00 UTC 2025
    - 3.7K bytes
    - Viewed (0)
  8. android/guava/src/com/google/common/cache/LoadingCache.java

       * {@code key}, simply waits for that thread to finish and returns its loaded value. Note that
       * multiple threads can concurrently load values for distinct keys.
       *
       * <p>Caches loaded by a {@link CacheLoader} will call {@link CacheLoader#load} to load new values
       * into the cache. Newly loaded values are added to the cache using {@code
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Sat Dec 21 03:10:51 UTC 2024
    - 8.3K bytes
    - Viewed (0)
  9. android/guava/src/com/google/common/base/Predicate.java

     * appropriate primitive specialization such as {@code IntPredicate}) instead whenever possible.
     * Otherwise, at least reduce <i>explicit</i> dependencies on this type by using lambda expressions
     * or method references instead of classes, leaving your code easier to migrate in the future.
     *
     * <p>To use a reference of this type (say, named {@code guavaPredicate}) in a context where {@code
     * java.util.function.Predicate} is expected, use the method reference {@code
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Wed Jun 18 15:22:00 UTC 2025
    - 3.4K bytes
    - Viewed (0)
  10. android/guava/src/com/google/common/base/Supplier.java

     * appropriate primitive specialization such as {@code IntSupplier}) instead whenever possible.
     * Otherwise, at least reduce <i>explicit</i> dependencies on this type by using lambda expressions
     * or method references instead of classes, leaving your code easier to migrate in the future.
     *
     * <p>To use an existing supplier instance (say, named {@code supplier}) in a context where the
    Registered: Fri Dec 26 12:43:10 UTC 2025
    - Last Modified: Thu Jun 19 17:20:48 UTC 2025
    - 3K bytes
    - Viewed (0)
Back to top