labels.chat_step_intent=Analizar
labels.chat_step_search=Buscar
labels.chat_step_evaluate=Evaluar
labels.chat_step_fetch=Obtener
labels.chat_step_answer=Responder
labels.chat_input_hint=Enter para enviar, Shift+Enter para nueva línea
labels.chat_send=Enviar mensaje
labels.chat_retry=Reintentar
labels.chat_dismiss=Cerrar
labels.chat_copied=¡Copiado!
labels.chat_copy_failed=Error al copiar

### Provider-specific Notes

#### Various

   Core changes:

  * Support for load balancers with source ranges

#### AWS

Core changes:

  * Support for ELBs with complex configurations: better subnet selection with
multiple subnets, and internal ELBs
  * Support for VPCs with private dns names
  * Multiple fixes to EBS volume mounting code for robustness, and to support

  }

  /**
   * Not supported. Use {@link #naturalOrder}, which offers better type-safety, instead. This method
   * exists only to hide {@link ImmutableSet#builder} from consumers of {@code ImmutableSortedSet}.
   *
   * @throws UnsupportedOperationException always
   * @deprecated Use {@link ImmutableSortedSet#naturalOrder}, which offers better type-safety.
   */
  @DoNotCall("Use naturalOrder")
  @Deprecated

   * completely unused, and an expensive acquire(100) request comes. It would be nonsensical to just
   * wait for 100 seconds, and /then/ start the actual task. Why wait without doing anything? A much
   * better approach is to /allow/ the request right away (as if it was an acquire(1) request
   * instead), and postpone /subsequent/ requests as needed. In this version, we allow starting the

         * today). TODO: b/392974826 - Check for the existence of Unsafe and its methods
         * reflectively before attempting to access UnsafeComparator. Or, better yet, allow
         * UnsafeComparator to still initialize correctly even if Unsafe is unavailable. This would
         * protect against users that automatically preinitialize internal classes that they've seen

Also, **automatically generated clients** will have simpler interfaces, so that the developers communicating with your API can have a much better time working with your API. 😎

///

All the fields in `HeroPublic` are the same as in `HeroBase`, with `id` declared as `int` (not `None`):

* `id`
* `name`
* `age`

## Useful tips

### How Gradle Works

We have [a series of blog](https://blog.gradle.org/how-gradle-works-1) that explains how Gradle works.
This may help you better understand and contribute to Gradle.

### Debugging Gradle

See the [Debugging Gradle](./contributing/Debugging.md) guide for tips on debugging Gradle.

   *
   * <p>If {@code expectedSize} is exactly the number of entries added to the builder before {@link
   * Builder#build} is called, the builder is likely to perform better than an unsized {@link
   * #builder()} would have.
   *
   * <p>It is not specified if any performance benefits apply if {@code expectedSize} is close to,
   * but not exactly, the number of entries added to the builder.

{* ../../docs_src/bigger_applications/app_an_py310/dependencies.py hl[3,6:8] title["app/dependencies.py"] *}

/// tip

We are using an invented header to simplify this example.

But in real cases you will get better results using the integrated [Security utilities](security/index.md).

///

## Another module with `APIRouter` { #another-module-with-apirouter }

labels.chat_step_intent=Analisar
labels.chat_step_search=Pesquisar
labels.chat_step_evaluate=Avaliar
labels.chat_step_fetch=Obter
labels.chat_step_answer=Responder
labels.chat_input_hint=Enter para enviar, Shift+Enter para nova linha
labels.chat_send=Enviar mensagem
labels.chat_retry=Tentar novamente
labels.chat_dismiss=Fechar
labels.chat_copied=Copiado!
labels.chat_copy_failed=Falha ao copiar