HandlerClearUploadID
	HandlerCheckParts3

	// Add more above here ^^^
	// If all handlers are used, the type of Handler can be changed.
	// Handlers have no versioning, so non-compatible handler changes must result in new IDs.
	handlerTest
	handlerTest2
	handlerLast
)

// handlerPrefixes are prefixes for handler IDs used for tracing.
// If a handler is not listed here, it will be traced with "grid" prefix.

         * Returns the option followed by a string representation of the given path elements.
         * The path elements are separated by an option-specific or platform-specific separator.
         * If the given {@code paths} argument contains no element, then this method returns an empty string.
         * The paths are not quoted.
         *
         * @param paths the path to format as a string

    /**
     * Guess called name to try for session establishment. These
     * methods are used by the smb package.
     *
     * @return guessed name
     */
    String firstCalledName();

    /**
     * Guess next called name to try for session establishment. These
     * methods are used by the smb package.
     *
     * @param tc the transport context to use for name resolution
     *

import static java.lang.annotation.ElementType.TYPE;
import static java.lang.annotation.RetentionPolicy.RUNTIME;

/**
 * Specifies the priority of a bean implementation when multiple implementations
 * of the same type are available.
 * <p>
 * Higher values indicate higher priority. When multiple implementations of the same
 * type exist, the one with the highest priority will be selected for injection.
 * <p>
 * Example usage:
 * <pre>

  They are replaced in Maven 4 with Maven 4 API Core's {{{../../api/maven-api-core/apidocs/org/apache/maven/api/Type.html}Dependency Types}},
  with default values defined in {{{../../compat/maven-resolver-provider/apidocs/org/apache/maven/repository/internal/type/DefaultTypeProvider.html}DefaultTypeProvider}}.

  For compatibility, legacy Maven 3 artifact handlers are still provided:

# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
daysUntilClose: 15

# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
onlyLabels: []

# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
exemptLabels:
  - "security"
  - "pending discussion"

body:
  - type: textarea
    id: jobs
    attributes:
      label: Which jobs are failing?
      placeholder: |
        Please only use this template for submitting reports about continuously failing tests or jobs in Kubernetes CI.
    validations:
      required: true

  - type: textarea
    id: tests
    attributes:
      label: Which tests are failing?
    validations:
      required: true

  - type: textarea

## Additional Response with `model` { #additional-response-with-model }

You can pass to your *path operation decorators* a parameter `responses`.

It receives a `dict`: the keys are status codes for each response (like `200`), and the values are other `dict`s with the information for each of them.

Each of those response `dict`s can have a key `model`, containing a Pydantic model, just like `response_model`.

 * - Happy path with default and custom options.
 * - Null/empty/ignored name parameter handling.
 * - Null options edge case.
 * - Repeated calls equivalence and instance separation.
 * - Interaction check that passed options are not mutated.
 */
@ExtendWith(MockitoExtension.class)
class StaticJAASConfigurationTest {

    // Constants used in assertions

        smbComNtTransaction.dataOffset = 200;

        byte[] dst = new byte[100];
        smbComNtTransaction.writeParameterWordsWireFormat(dst, 0);

        // Check that offsets are zero when counts are zero
        assertEquals(0, SmbComTransaction.readInt4(dst, 23), "parameterOffset should be 0 when parameterCount is 0");