// Given/When: Creating NdrShort with zero
            NdrShort ndrShort = new NdrShort(0);

            // Then: Value should be zero
            assertEquals(0, ndrShort.value);
        }

        @Test
        @DisplayName("Should handle maximum byte value correctly")
        void testConstructorMaxByte() {
            // Given/When: Creating NdrShort with max byte value

     *
     * @param address the NetBIOS address to connect to
     * @param port the port number, or 0 for the default NetBIOS session service port
     * @throws IOException if an I/O error occurs while creating the socket
     */
    public NbtSocket(final NbtAddress address, final int port) throws IOException {
        this(address, port, null, 0);
    }

    /**

{* ../../docs_src/settings/app02/test_main.py hl[9:10,13,21] *}

In the dependency override we set a new value for the `admin_email` when creating the new `Settings` object, and then we return that new object.

Then we can test that it is used.

## Reading a `.env` file { #reading-a-env-file }

> What’s the history of this project? It seems to have come from nowhere to awesome in a few weeks [...]

Here's a little bit of that history.

## Alternatives { #alternatives }

I have been creating APIs with complex requirements for several years (Machine Learning, distributed systems, asynchronous jobs, NoSQL databases, etc), leading several teams of developers.

    return new NullRemovalListener<>();
  }

  /** Type-inferring factory method for creating a {@link QueuingRemovalListener}. */
  @GwtIncompatible // ConcurrentLinkedQueue
  static <K, V> QueuingRemovalListener<K, V> queuingRemovalListener() {
    return new QueuingRemovalListener<>();
  }

  /** Type-inferring factory method for creating a {@link CountingRemovalListener}. */

        assertEquals(expectedFlags, context.ntlmsspFlags);
    }

    @Test
    void testInitSecContext_state1_type1Message() throws Exception {
        // Test the first step of context initialization (creating Type 1 message)
        when(mockAuth.getDomain()).thenReturn(domain);
        NtlmContext context = new NtlmContext(mockAuth, true);
        byte[] type1Token = context.initSecContext(new byte[0], 0, 0);

    @DisplayName("SamrCloseHandle Tests")
    class SamrCloseHandleTests {

        @Test
        @DisplayName("Should construct with correct opnum")
        void testConstructorAndOpnum() {
            // When: Creating close handle message
            samr.SamrCloseHandle message = new samr.SamrCloseHandle(mockPolicyHandle);

            // Then: Should have correct opnum and handle
            assertEquals(0x01, message.getOpnum());

![Choose Immutability Days for Object Store](https://raw.githubusercontent.com/minio/minio/master/docs/integrations/veeam/screenshots/object_store_immutable_days.png)

### Creating the Scale-out Backup Repository

- Under the Backup Infrastructure view, click on Scale-out Repositories and click the Add Scale-out Repository button on the ribbon.

- Follow the on screen wizard

    @DisplayName("SamrCloseHandle Tests")
    class SamrCloseHandleTests {

        @Test
        @DisplayName("Should construct with correct opnum")
        void testConstructorAndOpnum() {
            // When: Creating close handle message
            samr.SamrCloseHandle message = new samr.SamrCloseHandle(mockPolicyHandle);

            // Then: Should have correct opnum and handle
            assertEquals(0x01, message.getOpnum());

     * Changes include renaming, creating, or deleting a file.
     */
    int FILE_NOTIFY_CHANGE_FILE_NAME = 0x00000001;

    /**
     * Any directory-name change in the watched directory or subtree causes a change notification wait operation to
     * return. Changes include creating or deleting a directory.
     */
    int FILE_NOTIFY_CHANGE_DIR_NAME = 0x00000002;

    /**