*/
    @Nullable
    OutputStream stdErr();

    /**
     * Returns {@code true} if this call happens in "embedded" mode, for example by another application that
     * embeds Maven. When running in "embedded" mode, Maven will not try to grab system terminal and will use
     * provided {@link #stdIn()} or {@link InputStream#nullInputStream()} as standard in stream.
     */

        assertEquals(25, SMBUtil.readInt2(buffer, bodyOffset));

        // Verify session binding flag (0x1)
        assertEquals(0x1, buffer[bodyOffset + 2]);

        // Verify security mode
        assertEquals(TEST_SECURITY_MODE, buffer[bodyOffset + 3]);

        // Verify capabilities
        assertEquals(TEST_CAPABILITIES, SMBUtil.readInt4(buffer, bodyOffset + 4));

* `>`: cualquier cosa impresa en el terminal por el comando a la izquierda de `>` no debería imprimirse, sino escribirse en el archivo que va a la derecha de `>`
* `.gitignore`: el nombre del archivo donde debería escribirse el texto

Y `*` para Git significa "todo". Así que, ignorará todo en el directorio `.venv`.

Ese comando creará un archivo `.gitignore` con el contenido:

```gitignore
*
```

  }

  private static ImmutableSet<Field> httpHeadersFields() {
    ImmutableSet.Builder<Field> builder = ImmutableSet.builder();
    for (Field field : HttpHeaders.class.getDeclaredFields()) {
      /*
       * Coverage mode generates synthetic fields.  If we ever add private
       * fields, they will cause similar problems, and we may want to switch
       * this check to isAccessible().
       */

   * <<<.mvn/extensions.xml>>> containing {{{./core-extensions.html}a list of extensions}},

 * since 3.5.0, output is colorized by default, with color disabled in batch mode: see
   {{{/shared/maven-shared-utils/apidocs/org/apache/maven/shared/utils/logging/package-summary.html}styled message API}}

            testSummaryMaxChars = maxChars;
        }

        String testBuildAssistantHistoryContent(final ChatMessage msg, final String mode, final int assistantMaxChars,
                final int summaryMaxChars) {
            return buildAssistantHistoryContent(msg, mode, assistantMaxChars, summaryMaxChars);
        }

        List<LlmMessage> testExtractHistory(final ChatSession session) {

    private static final int FLAGS_RETURN_ADDITIONAL_INFO = 0x01;
    private static final int FLAGS_REQUEST_OPLOCK = 0x02;
    private static final int FLAGS_REQUEST_BATCH_OPLOCK = 0x04;

    // Access Mode Encoding for desiredAccess
    private static final int SHARING_COMPATIBILITY = 0x00;
    private static final int SHARING_DENY_READ_WRITE_EXECUTE = 0x10;
    private static final int SHARING_DENY_WRITE = 0x20;

			if prefix != 0 || scale != 0 {
				p.errorf("illegal address mode for register pair")
				return
			}
			a.Type = obj.TYPE_REGREG
			a.Offset = int64(r2)
			// Nothing may follow
			return
		}
		if p.arch.Family == sys.PPC64 {
			// Special form for PPC64: (R1+R2); alias for (R1)(R2).
			if prefix != 0 || scale != 0 {
				p.errorf("illegal address mode for register+register")
				return
			}

Embora qualquer outro parâmetro declarado normalmente (o corpo da requisição com um modelo Pydantic, por exemplo) ainda seria validado, convertido, anotado, etc.

Mas há situações específicas onde é útil utilizar o objeto `Request`.

## Utilize o objeto `Request` diretamente { #use-the-request-object-directly }

Vamos imaginar que você deseja obter o endereço de IP/host do cliente dentro da sua *função de operação de rota*.

	Location string   `xml:"LocationConstraint"`
}

// DeleteObjectsRequest - xml carrying the object key names which needs to be deleted.
type DeleteObjectsRequest struct {
	// Element to enable quiet mode for the request
	Quiet bool
	// List of objects to be deleted
	Objects []ObjectToDelete `xml:"Object"`