not active (in most cases, localhost should be available, even if the rest of
  the network is not). Therefore, let's concentrate on the state where no
  network <beyond localhost> exists, and leave the more extreme state to users
  to diagnose and correct as necessary.

* Why is Offline Mode Important?

  Offline mode is essential for breaking the requirement that m2 operate in a

        @Override
        public boolean isError() {
            return this.error;
        }

        @Override
        public void error() {
            this.error = true;
        }

        // Setter methods for testing
        public void setGrantedCredits(int grantedCredits) {
            this.grantedCredits = grantedCredits;
        }

        public void setErrorCode(int errorCode) {

        assertEquals(0, transport.getNumSessions());
    }

    @Test
    @DisplayName("isDisconnected / isFailed reflect socket and state")
    void connectionStateChecks() throws Exception {
        // Arrange: simulate connected state and open socket
        setField(transport, "state", 3); // connected
        Socket s = mock(Socket.class);
        when(s.isClosed()).thenReturn(false);
        setField(transport, "socket", s);

    super.tearDown();
  }

  public void testListenerDoesNotRunUntilTaskCompletes() throws Exception {

    // Test default state of not started.
    assertEquals(1, listenerLatch.getCount());
    assertFalse(task.isDone());
    assertFalse(task.isCancelled());

    // Start the task to put it in the RUNNING state.  Have to use a separate
    // thread because the task will block on the task latch after unblocking
    // the run latch.

        }
    }

    @Nested
    @DisplayName("Response State Tests")
    class ResponseStateTests {

        @BeforeEach
        void setup() {
            testBlock = new TestServerMessageBlock(mockConfig);
        }

        @Test
        @DisplayName("Test received state")
        void testReceivedState() {
            assertFalse(testBlock.isReceived());

# Concurrence et les mots-clés async et await

Cette page vise à fournir des détails sur la syntaxe `async def` pour les *fonctions de chemins* et quelques rappels sur le code asynchrone, la concurrence et le parallélisme.

## Vous êtes pressés ?

<abbr title="'too long; didn't read' en anglais, ou 'trop long ; j'ai pas lu'"><strong>TL;DR :</strong></abbr>

Si vous utilisez des bibliothèques tierces qui nécessitent d'être appelées avec `await`, telles que :

    public String[] groups;

    /** Version number for optimistic locking */
    public String versionNo;

    /**
     * Clears all pagination state and search criteria.
     * Resets the pager to its initial state with default values.
     */
    public void clear() {
        allRecordCount = 0;
        allPageCount = 0;
        existPrePage = false;
        existNextPage = false;

     * @return the lease key
     */
    public Smb2LeaseKey getLeaseKey() {
        return leaseKey;
    }

    /**
     * Gets the lease state granted by the server
     * @return the granted lease state
     */
    public int getLeaseState() {
        return leaseState;
    }

    /**
     * Gets the lease flags from the server response
     * @return the lease flags
     */

      extends AbstractFuture<T> {
    private @Nullable InCompletionOrderState<T> state;

    private InCompletionOrderFuture(InCompletionOrderState<T> state) {
      this.state = state;
    }

    @Override
    public boolean cancel(boolean interruptIfRunning) {
      InCompletionOrderState<T> localState = state;
      if (super.cancel(interruptIfRunning)) {
        /*

  /**
   * This field encodes the current state of the future.
   *
   * <p>The valid values are:
   *
   * <ul>
   *   <li>{@code null} initial state, nothing has happened.
   *   <li>{@link Cancellation} terminal state, {@code cancel} was called.
   *   <li>{@link Failure} terminal state, {@code setException} was called.
   *   <li>{@link DelegatingToFuture} intermediate state, {@code setFuture} was called.