assertEquals(0x20, nbtAddress.getNameType());
    }

    @Test
    void testHashCode() {
        // Test hashCode consistency
        mockName = new Name(mockConfig, "TEST1", 0x20, null);
        Name mockName2 = new Name(mockConfig, "TEST2", 0x20, null);

 *       in the hash code should be as evenly "spread out" through the hash code's bits as possible.
 *       The result is that, for example, when choosing a bucket in a hash table of size 2^8,
 *       <i>any</i> eight bits could be consistently used.
 *   <li><b>cryptographic:</b> certain hash functions such as {@link Hashing#sha512} are designed to
 *       make it as infeasible as possible to reverse-engineer the input that produced a given hash

            byte[] encodedPath = new byte[pathBytes.length];
            bb.get(encodedPath);
            assertArrayEquals(pathBytes, encodedPath);
        }

        @Test
        @DisplayName("Should encode consistently on multiple calls")
        void testEncodeIdempotency() {
            String path = "\\\\server\\share";
            buffer = new DfsReferralRequestBuffer(path, 3);

            byte[] dst1 = new byte[buffer.size()];

Keep in mind that when using `Query` inside of `Annotated` you cannot use the `default` parameter for `Query`.

Instead, use the actual default value of the function parameter. Otherwise, it would be inconsistent.

For example, this is not allowed:

```Python
q: Annotated[str, Query(default="rick")] = "morty"
```

...because it's not clear if the default value should be `"rick"` or `"morty"`.

# FastAPI dans des conteneurs - Docker { #fastapi-in-containers-docker }

Lors du déploiement d'applications FastAPI, une approche courante consiste à construire une **image de conteneur Linux**. C'est généralement fait avec [**Docker**](https://www.docker.com/). Vous pouvez ensuite déployer cette image de conteneur de plusieurs façons possibles.

    public static final int SMB2_LEASE_FULL           = 0x07;  // RWH
}
```

### 3.2 Lease Versions
- **Lease V1**: Basic lease support (SMB 3.0)
- **Lease V2**: Adds epoch support for better consistency (SMB 3.0.2+)

## 4. Data Structures

### 4.1 Lease Key Structure
```java
package jcifs.internal.smb2.lease;

import java.security.SecureRandom;
import java.util.Arrays;

public class Smb2LeaseKey {

            assertFalse((executeMask & ACE.FILE_WRITE_DATA) != 0, "Execute should not include write access");
        }

        @Test
        @DisplayName("Should validate documented bit comment consistency")
        void shouldValidateDocumentedBitComments() {
            // Verify that comments in source match actual constant values (not bit positions)

replication status is reflected as `PENDING`.

If 3 or more targets are participating in active-active replication, the replication configuration for replica metadata sync, delete marker replication and delete replication should match to avoid inconsistent picture between the clusters. It is not recommended to turn on asymmetric replication - for e.g. if three sites A,B,C are participating in replication, it would be better to avoid replication setups like A -> [B, C], B -> A. In this particular...

L'une des principales fonctionnalités nécessaires aux systèmes API est la « <dfn title="aussi appelé : marshalling, conversion">sérialisation</dfn> » des données, qui consiste à prendre les données du code (Python) et à
les convertir en quelque chose qui peut être envoyé sur le réseau. Par exemple, convertir un objet contenant des

   *
   * <p>Unlike the other {@code EndpointPair}-accepting methods, this method does not throw if the
   * endpoints are unordered and the graph is directed; it simply returns {@code false}. This is for
   * consistency with the behavior of {@link Collection#contains(Object)} (which does not generally
   * throw if the object cannot be present in the collection), and the desire to have this method's