</excludePackageNames>
          <!-- Ignore some tags that are found in Java 11 sources but not recognized... under -source 8, I think it was? I can no longer reproduce the failure. -->
          <tags>
            <tag>
              <name>apiNote</name>
              <placement>X</placement>
            </tag>
            <tag>
              <name>implNote</name>

                    if (waitForState(transport) == 2) {
                        // finished connecting
                        return null;
                    }
                    // failure to connect
                    throw new SmbException("Tree disconnected while waiting for connection");
                }
                if (before == 2) {
                    // concurrently connected

   *   Iterator<E> i = queue.iterator(); // Must be in synchronized block
   *   while (i.hasNext()) {
   *     foo(i.next());
   *   }
   * }
   * }
   *
   * <p>Failure to follow this advice may result in non-deterministic behavior.
   *
   * <p>The returned queue will be serializable if the specified queue is serializable.
   *

     *
     * @param userMessage the user's original message
     * @param failedQuery the query that failed
     * @param failureReason the reason for failure ("no_results" or "no_relevant_results")
     * @param history the conversation history
     * @return a new query string, or the userMessage if regeneration fails
     */

                id = name
                executionMode = ExecutionMode.RUN_ONLY_ON_FAILURE
                conditions {
                    equals("teamcity.build.step.status.$GRADLE_RUNNER_STEP_NAME", "failure")
                    equals("teamcity.build.step.status.$GRADLE_RETRY_RUNNER_STEP_NAME", "success")
                }
                scriptContent =
                    """

server in a given timeframe for whatever reasons (networking issue, machine
failure, etc.). Normally when kube-up script will encounter even one NotReady
node it will fail, even though the cluster most likely will be working. We
added an environmental variable to kube-up ALLOWED\_NOTREADY\_NODES that
defines the number of nodes that if not Ready in time won’t cause kube-up
failure.
  * “kubectl rolling-update” only supports Replication Controllers (it doesn’t

        assertThrows(SmbException.class, () -> tree.treeConnect(null, null));
        // After failure, state should be reset to disconnected
        assertEquals(0, tree.connectionState);
    }

    @Test
    void testSend() throws SmbException {
        SmbTree tree = new SmbTree(session, "testShare", "A:");

    val event = listener.removeUpToEvent(ConnectionEvent.ConnectFailed::class.java)
    assertThat(event.route.socketAddress).isEqualTo(expectedAddress)

    // Read error: ssl=0x7fd1d8d0fee8: Failure in SSL library, usually a protocol error
    if (!platform.isConscrypt()) {
      assertThat(event.exception.message).isIn(
        "Unexpected handshake message: client_hello",

	if algo != HighwayHash256S {
		h := algo.New()
		if n, err := io.Copy(h, r); err != nil || n != wantSize {
			// Premature failure in reading the object, file is corrupt.
			return errFileCorrupt
		}
		if !bytes.Equal(h.Sum(nil), want) {
			return errFileCorrupt
		}
		return nil
	}

	h := algo.New()

    }

    /**
     * Deletes a role setting by ID.
     *
     * @param id the ID of the role setting to delete
     * @return JSON response indicating success or failure
     */
    // DELETE /api/admin/role/setting/{id}
    @Execute
    public JsonResponse<ApiResult> delete$setting(final String id) {
        final Role entity = roleService.getRole(id).orElseGet(() -> {