* methods like {@link #state}, {@link #failureCause} and notably {@link #toString} can be run
   * without grabbing the lock.
   *
   * <p>To update this field correctly the lock must be held to guarantee that the state is
   * consistent.
   */
  private volatile StateSnapshot snapshot = new StateSnapshot(NEW);

  /** Constructor for use by subclasses. */

  (three value logic: yes, no, don't-care). The requiresOnline
  field in the mojo descriptor has the following semantics:

  [true] Online status is required for this mojo to function
         correctly.

  [false] <<(Default)>> Either status is acceptable for the mojo to
          execute. It doesn't care.

  The majority of mojos will leave the requiresOnline == false,

        try {
            // Should be able to decrypt with same salt and password
            char[] decrypted = storage2.decryptCredentials(encrypted);
            assertArrayEquals(plaintext, decrypted, "Should decrypt correctly with same salt and password");
            Arrays.fill(decrypted, '\0');
        } finally {
            storage2.close();
        }

        Arrays.fill(plaintext, '\0');
    }

    @Test

    assertEquals(1, Queues.newLinkedBlockingQueue(1).remainingCapacity());
    assertEquals(11, Queues.newLinkedBlockingQueue(11).remainingCapacity());
  }

  /** Checks that #drain() invocations behave correctly for a drained (empty) queue. */
  private void assertDrained(BlockingQueue<Object> q) {
    assertThat(q.peek()).isNull();
    assertInterruptibleDrained(q);
    assertUninterruptibleDrained(q);
  }

    fi
  else
    JAVACMD="$(
      \unset -f command 2>/dev/null
      \command -v java
    )"
  fi
fi

if [ ! -x "$JAVACMD" ]; then
  echo "Error: JAVA_HOME is not defined correctly." >&2
  echo "  We cannot execute $JAVACMD" >&2
  exit 1
fi

if [ -z "$JAVA_HOME" ]; then
  echo "Warning: JAVA_HOME environment variable is not set." >&2
fi

    @DisplayName("Constructor acquires tree connection; getConfig/isConnected delegate")
    void constructorAndSimpleDelegations() {
        // Ensures constructor acquires tree connection and simple delegate methods forward correctly
        // Verify constructor invoked acquire once
        verify(treeConnection, times(1)).acquire();

        // getConfig delegates
        when(treeConnection.getConfig()).thenReturn(config);

            // https://github.com/gradle/gradle-private/issues/3991
            System.out.println("Gradle runner not finished correctly (the build may be canceled). Fall back to KILL_ALL_GRADLE_PROCESSES.");
            executionMode = ExecutionMode.KILL_ALL_GRADLE_PROCESSES;
        }
    }

Um exemplo difícil de literais de string em trechos de código: `f"I like {'oranges' if orange else "apples"}"`

Pesado: `Yesterday, my friend wrote: "If you spell incorrectly correctly, you have spelled it incorrectly". To which I answered: "Correct, but 'incorrectly' is incorrectly not '"incorrectly"'"`

////

//// tab | Informações

... No entanto, as aspas dentro de trechos de código devem permanecer como estão.

////

      sourceResult = getDone(localInputFuture);
    } catch (CancellationException e) {
      // TODO(user): verify future behavior - unify logic with getFutureValue in AbstractFuture. This
      // code should be unreachable with correctly implemented Futures.
      // Cancel this future and return.
      // At this point, inputFuture is cancelled and outputFuture doesn't exist, so the value of
      // mayInterruptIfRunning is irrelevant.
      cancel(false);

If you generate a client for a FastAPI app using tags, it will normally also separate the client code based on the tags.

This way, you will be able to have things ordered and grouped correctly for the client code:

<img src="/img/tutorial/generate-clients/image06.png">

In this case, you have:

* `ItemsService`
* `UsersService`

### Client Method Names { #client-method-names }