result = response.readParametersWireFormat(smallBuffer, 0, -1);
        assertEquals(0, result);
    }

    @Test
    @DisplayName("Test command type is correct")
    void testCommandType() {
        // Verify that the command is not set in constructor (defaults to 0)
        assertEquals(0, response.getCommand());

        // Verify we can change the subcommand

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

rootUser=rootuser,rootPassword=rootpass123 --generate-name minio/minio ``` The command deploys MinIO on the Kubernetes cluster in the default configuration. The [configuration](#configuration) section lists the parameters that can be configured during installation. Upgrading the Chart ---------- You can use Helm to update MinIO version in a live release. Assuming your release is named as `my-release`, get the values using the command: ```bash helm get values my-release > old_values.yaml ``` Then change the...

            throw new SmbException("Invalid SMB protocol identifier");
        }

        // Validate command is in valid range
        if (command < 0 || command > 255) {
            failedValidations.incrementAndGet();
            throw new SmbException("Invalid command code: " + command);
        }
    }

    /**
     * Validate array size before allocation
     *

    void testConstructor() {
        assertEquals(testDomain, netServerEnum2.domain);
        assertEquals(testServerTypes, netServerEnum2.serverTypes);
        assertEquals(ServerMessageBlock.SMB_COM_TRANSACTION, netServerEnum2.command);
        assertEquals(SmbComTransaction.NET_SERVER_ENUM2, netServerEnum2.subCommand);
        assertEquals("\\PIPE\\LANMAN", netServerEnum2.name);
        assertEquals(8, netServerEnum2.maxParameterCount);

        @DisplayName("Should create with configuration and command")
        void testConstructorWithConfigAndCommand() {
            int command = ServerMessageBlock2.SMB2_NEGOTIATE;
            ServerMessageBlock2 msg = new TestServerMessageBlock2(mockConfig, command);
            assertNotNull(msg);
            assertEquals(mockConfig, msg.getConfig());
            assertEquals(command, msg.getCommand());
        }
    }

## Uninstalling the Chart

Assuming your release is named as `my-release`, delete it using the command:

```bash
helm delete my-release
```

or

```bash
helm uninstall my-release
```