Então, você pode adicionar dados extras para o esquema gerado automaticamente.

Por exemplo, você poderia optar por ler e validar a requisição com seu próprio código, sem utilizar funcionalidades automatizadas do FastAPI com o Pydantic, mas você ainda pode quere definir a requisição no esquema OpenAPI.

Você pode fazer isso com `openapi_extra`:

jcifs.smb.client.useUnicode=true
jcifs.smb.client.maxMpxCount=10
```

### Usage with Properties

```java
Properties props = new Properties();
props.setProperty("jcifs.smb.client.domain", "MYDOMAIN");
props.setProperty("jcifs.smb.client.useLeases", "true");

Configuration config = new PropertyConfiguration(props);
CIFSContext context = new BaseContext(config);
```

## Development

### Build Commands
```bash

  }

  public void testBase64LenientPadding() {
    testDecodes(base64(), "Zg", "f");
    testDecodes(base64(), "Zg=", "f");
    testDecodes(base64(), "Zg==", "f"); // proper padding length
    testDecodes(base64(), "Zg===", "f");
    testDecodes(base64(), "Zg====", "f");
  }

  public void testBase64InvalidDecodings() {
    // These contain bytes not in the decodabet.

import java.io.IOException;
import java.io.InputStream;
import java.io.Reader;
import junit.framework.TestCase;
import org.jspecify.annotations.NullUnmarked;

/**
 * Unit tests for {@link Closeables}.
 *
 * <p>Checks proper closing behavior, and ensures that IOExceptions on Closeable.close() are not
 * propagated out from the {@link Closeables#close} method if {@code swallowException} is true.
 *
 * @author Michael Lancaster
 */
@NullUnmarked

* **Historical compatibility**: Existing public API methods that are part of Gradle's stable API cannot be renamed due to backward compatibility requirements (though new APIs should use American English)
* **Proper nouns and quotes**: Names of organizations, products, or quoted text that use different conventions

## Status

ACCEPTED

## Consequences

### Positive Consequences

 *   <li>Handle project forking states</li>
 * </ul>
 *
 * The service maintains the mutable state of projects as they progress through
 * their build lifecycle, ensuring thread-safety and proper state management.
 * All implementations must be thread-safe as they may be accessed concurrently
 * during parallel builds.
 *
 * @since 4.0.0
 * @see org.apache.maven.api.services.ProjectBuilder
 * @see Project
 */

    @BeforeEach
    public void setUp() {
        MockitoAnnotations.openMocks(this);
    }

    @Test
    public void testConstructorInitializesFields() {
        // Test constructor initialization with proper expectations
        String pipeName = "\\\\pipe\\testPipe";
        TransWaitNamedPipe pipe = new TransWaitNamedPipe(pipeName);

        // Verify the name is set correctly
        assertEquals(pipeName, pipe.name);

 * Manages a pool of byte buffers to reduce garbage collection overhead.
 *
 * Performance optimizations:
 * - Uses ConcurrentLinkedQueue for O(1) operations
 * - Lock-free operations for better concurrency
 * - Proper buffer validation and limits
 */
public class BufferCache {

    /**
     * Private constructor to prevent instantiation of this utility class.
     */
    private BufferCache() {

            // Close the digest
            digest.close();

            // Verify operations fail after close
            byte[] data = new byte[128];
            // Initialize the data buffer with proper SMB2 header structure
            SMBUtil.writeInt4(0xFE534D42, data, 0); // SMB2 signature
            SMBUtil.writeInt4(0x0000, data, 12); // Command = 0
            SMBUtil.writeInt4(0x0000, data, 16); // Flags = 0

    }

    /**
     * Determines whether the current request is authorized to access the API endpoint.
     * This default implementation returns false, requiring subclasses to override
     * and implement proper access control logic.
     *
     * @return true if access is allowed, false otherwise
     */
    protected boolean isAccessAllowed() {
        return false;
    }