}

    @Test
    public void test_nestedExceptions() {
        // Test nested exception handling
        Exception innerCause = new IllegalArgumentException("Invalid parameter");
        RuntimeException middleCause = new RuntimeException("Processing failed", innerCause);
        ThemeException exception = new ThemeException("Theme operation failed", middleCause);

 *
 * Neither of the built-in URL models offer direct access to path segments or query parameters.
 * Manually using `StringBuilder` to assemble these components is cumbersome: do '+' characters get
 * silently replaced with spaces? If a query parameter contains a '&', does that get escaped?
 * By offering methods to read and write individual query parameters directly, application
 * developers are saved from the hassles of encoding and decoding.
 *

              <artifactId>${project.artifactId}</artifactId>
              <version>${maven.baseline}</version>
            </dependency>
          </oldVersion>
          <parameter>
            <excludes>
              <!--              <exclude>org.apache.maven.model.building.DefaultModelBuilder#DefaultModelBuilder():CONSTRUCTOR_REMOVED</exclude>-->

          val message = record.message
          val parameters = record.parameters

          if (parameters != null && !message.startsWith("Raw") && !message.startsWith("Plaintext")) {
            if (verbose) {
              println(record.message)
              println(record.parameters[0])
            }

            // JSSE logs additional messages as parameters that are not referenced in the log message.

            return null;
        }
    }

    /**
     * Retrieves the pipeline configuration parameter for a given config ID.
     * The pipeline parameter is extracted from the crawling configuration's parameter map.
     *
     * @param configId the configuration ID to get the pipeline for

        byte[] dst = new byte[1024];

        // Initialize transaction buffer to avoid NPE
        transaction.setBuffer(new byte[SmbComTransaction.TRANSACTION_BUF_SIZE]);

        // Test parameter words wire format
        int paramWords = transaction.writeParameterWordsWireFormat(dst, 0);
        assertTrue(paramWords >= 0);

        // Test bytes wire format

 * that support Java 1.4 and before. Our library needs to do the bare minimum to accommodate such
 * types, though their use may still require an explicit type parameter and/or warning suppression.
 *
 * @author Kevin Bourrillion
 */
@SuppressWarnings({"ComparableType", "rawtypes"}) // https://github.com/google/guava/issues/989
@GwtCompatible
@NullMarked

Prefer to set the entrypoint in `pyproject.toml` when possible.

## Use `Annotated`

Always prefer the `Annotated` style for parameter and dependency declarations.

It keeps the function signatures working in other contexts, respects the types, allows reusability.

### In Parameter Declarations

Use `Annotated` for parameter declarations, including `Path`, `Query`, `Header`, etc.:

```python
from typing import Annotated

    @Throws(IOException::class)
    constructor(response: ResponseBody) : this(
      source = response.source(),
      boundary =
        response.contentType()?.parameter("boundary")
          ?: throw ProtocolException("expected the Content-Type to have a boundary parameter"),
    )

    @Throws(IOException::class)
    fun nextPart(): Part? {
      check(!closed) { "closed" }

      if (noMoreParts) return null

By default, the temporary security credentials created by AssumeRoleWithClientGrants last for one hour. However, use the optional DurationSeconds parameter to specify the duration of the credentials. This value varies from 900 seconds (15 minutes) up to the maximum session duration of 365 days.

## API Request Parameters

### Token