}
  }

  static void verifyThreadWasNotInterrupted() {
    // There is no thread interruption in GWT, so there's nothing to do.
  }

  static void clearInterrupt() {
    // There is no thread interruption in GWT, so there's nothing to do.
  }

  static <V extends @Nullable Object> V getDoneFromTimeoutOverload(Future<V> future)
      throws ExecutionException {

///

### "Mounting" là gì

"Mounting" có nghĩa là thêm một ứng dụng "độc lập" hoàn chỉnh vào một đường dẫn cụ thể, sau đó ứng dụng đó sẽ chịu trách nhiệm xử lý tất cả các đường dẫn con.

## Do not Separate Schemas { #do-not-separate-schemas }

Now, there are some cases where you might want to have the **same schema for input and output**.

Probably the main use case for this is if you already have some autogenerated client code/SDKs and you don't want to update all the autogenerated client code/SDKs yet, you probably will want to do it at some point, but maybe not right now.

* Ele então pega a **resposta** gerada pelo aplicativo (por alguma *operação de rota*).
* Ele pode fazer algo com essa **resposta** ou executar qualquer código necessário.
* Então ele retorna a **resposta**.

/// note | Detalhes técnicos

Se você tiver dependências com `yield`, o código de saída será executado *depois* do middleware.

You should do it after adding all your *path operations*.

{* ../../docs_src/path_operation_advanced_configuration/tutorial002.py hl[2, 12:21, 24] *}

/// tip

If you manually call `app.openapi()`, you should update the `operationId`s before that.

///

/// warning

If you do this, you have to make sure each one of your *path operation functions* has a unique name.

    attributes:
      label: "Screenshot"
      description: "Please paste a screenshot of the page."
    validations:
      required: false
  - type: textarea
    id: what-did-you-do
    attributes:
      label: "What did you do?"
      description: "If possible, provide a recipe for reproducing the error. Starting with a Private/Incognito tab/window may help rule out problematic browser extensions."
    validations:

        assertEquals(ServerMessageBlock.DEFAULT_FLAGS2, smbComNegotiate.flags2, "Constructor should set flags2 to DEFAULT_FLAGS2.");
    }

    /**
     * Test the writeParameterWordsWireFormat method.
     * This method should do nothing and return 0.
     */
    @Test
    void testWriteParameterWordsWireFormat() {
        byte[] dst = new byte[10];
        int dstIndex = 0;
        // The method should return 0 as it writes no parameter words

/// tip | Dica

#!/usr/bin/env bash

# shellcheck disable=SC2120
exit_1() {
	cleanup

	for site in sitea siteb; do
		echo "$site server logs ========="
		cat "/tmp/${site}_1.log"
		echo "==========================="
		cat "/tmp/${site}_2.log"
	done

	exit 1
}

cleanup() {
	echo -n "Cleaning up instances of MinIO ..."
	pkill -9 minio || sudo pkill -9 minio
	rm -rf /tmp/sitea
	rm -rf /tmp/siteb
	echo "done"
}

cleanup

You can declare that a parameter can accept `None`, but that it's still required. This would force clients to send a value, even if the value is `None`.

To do that, you can declare that `None` is a valid type but simply do not declare a default value:

{* ../../docs_src/query_params_str_validations/tutorial006c_an_py310.py hl[9] *}

## Query parameter list / multiple values { #query-parameter-list-multiple-values }