// contract of ExitException is that nothing needed by us
                throw e;
            } catch (Exception e) {
                // other exceptions (including InvokerException but sans Exit, see above): we need to inform user
                throw handleException(context, e);
            }
        } finally {
            Thread.currentThread().setContextClassLoader(oldCL);
            System.setProperties(oldProps);

        Please open Gradle Native-related issues on [the Gradle Native repository](https://github.com/gradle/gradle-native/issues)

        Provide a brief summary of the issue in the title above
  - type: textarea
    id: current-behavior
    attributes:
      label: Current Behavior
      description: Tell us what happens
    validations:
      required: true
  - type: textarea

            "2000-10-29 to 2000-10-30", // A date right around daylight savings time.
            "2000-06-01 to 2000-06-02"  // A date fully in one time zone. Should be much faster than above.
        }
    )
    public String range;

    @Param({ "java time", "es" })
    public String rounder;

    @Param({ "UTC", "America/New_York" })
    public String zone;

 *       }
 *     };
 * iteratorTester.test();
 * iteratorTester.testForEachRemaining();
 * }
 *
 * <p><b>Note</b>: It is necessary to use {@code IteratorTester.KnownOrder} as shown above, rather
 * than {@code KnownOrder} directly, because otherwise the code cannot be compiled.
 *
 * @author Kevin Bourrillion
 * @author Chris Povirk
 */
@GwtCompatible
@NullMarked

                    { 0x08bf0002, 0xC0000193 }, { 0x08c00002, 0xC0000070 }, { 0x08c10002, 0xC000006f }, { 0x08c20002, 0xC0000071 }, };

    /* These aren't really used by jCIFS -- the map above is used
     * to immediately map to NTSTATUS codes.
     */
    /**
     * Human-readable error messages corresponding to DOS error codes.
     * Array of descriptive strings for each DOS error condition.
     */

 *       String}.
 * </ul>
 *
 * This is the same behavior as type-variable usages have to Kotlin and to the Checker Framework.
 * Contrast the method above to:
 *
 * <ul>
 *   <li>methods whose return type is a type variable but which can never return {@code null},
 *       typically because the type forbids nullable type arguments: For example, {@code

   * tests, at least under whichever environment (JRE or Android) we see such problems.
   */

  @SuppressWarnings("WaitNotInLoop") // see comment above
  public void testConditionAwaitTimeoutExceeded() {
    Stopwatch stopwatch = Stopwatch.createStarted();
    Condition condition = TestCondition.create();

                    Arrays.asList(
                        "    exit $LASTEXITCODE",
                        "} catch {",
                        // catch if we have a failure to even run the script at all above, equivalent to set -e, sort of
                        "    echo $_.Exception.Message",
                        "    exit 1",
                        "}"
                    )
                );

    @Mock
    private TransactNamedPipeInputStream mockPipeIn;

    @InjectMocks
    private TransTransactNamedPipeResponse response;

    @BeforeEach
    void setUp() {
        // Initialize mocks created above
        MockitoAnnotations.openMocks(this);
        // We need to manually inject the mock as we are not using @InjectMocks on the constructor
        response = new TransTransactNamedPipeResponse(mockPipe);
    }

    /**

 * @since 2.0
 */
@GwtCompatible
public interface Predicate<T extends @Nullable Object> {
  /**
   * Returns the result of applying this predicate to {@code input} (Java 8+ users, see notes in the
   * class documentation above). This method is <i>generally expected</i>, but not absolutely
   * required, to have the following properties:
   *
   * <ul>
   *   <li>Its execution does not cause any observable side effects.