* or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *

 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *

 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * "License"); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 *
 *   http://www.apache.org/licenses/LICENSE-2.0
 *

        assertEquals(componentName, exception.getComponentName());
    }

    public void test_longComponentName() {
        // Test with a very long component name
        String longName = "com.example.very.long.package.name.with.many.nested.levels.MyVeryLongComponentNameThatExceedsNormalLength";
        ContainerNotAvailableException exception = new ContainerNotAvailableException(longName, null);

In your production system, you probably have a frontend created with a modern framework like React, Vue.js or Angular.

And to communicate using WebSockets with your backend you would probably use your frontend's utilities.

Or you might have a native mobile application that communicates with your WebSocket backend directly, in native code.

Or you might have any other way to communicate with the WebSocket endpoint.

---

        // The test will verify the method works with the actual ResourceUtil implementation

        // Test with reflection to access protected method
        List<String> names = testFactory.loadDataStoreNameList();
        assertTrue(names.isEmpty() || names.size() >= 0); // Will be empty due to ResourceUtil static method
    }

    // Test loadDataStoreNameList with malformed XML

        // Test with simple value
        SMBUtil.writeInt2(0x1234L, dst, 0);
        assertEquals((byte) 0x34, dst[0]);
        assertEquals((byte) 0x12, dst[1]);

        // Test with max value for 2 bytes
        SMBUtil.writeInt2(0xFFFFL, dst, 2);
        assertEquals((byte) 0xFF, dst[2]);
        assertEquals((byte) 0xFF, dst[3]);

        // Test with zero
        SMBUtil.writeInt2(0L, dst, 4);

        assertNotNull(sd.getOwnerGroupSid());
        assertNull(sd.getAces());
    }

    @Test
    @DisplayName("Test decode with owner SID only")
    void testDecodeWithOwnerSidOnly() throws SMBProtocolDecodingException {
        // Prepare buffer with owner SID only
        prepareMinimalSecurityDescriptorBuffer(testBuffer, 0, true, false, false);

        Properties props = new Properties();
        config = new PropertyConfiguration(props);
    }

    @Test
    @DisplayName("Test constructor with SMB_INFO_ALLOCATION")
    void testConstructorWithSmbInfoAllocation() {
        // Create instance with SMB_INFO_ALLOCATION
        trans2QueryFSInfo = new Trans2QueryFSInformation(config, FileSystemInformation.SMB_INFO_ALLOCATION);

        // Verify initialization

      - uses: actions/checkout@v5
        with:
          # To allow latest-changes to commit to the main branch
          token: ${{ secrets.FASTAPI_LATEST_CHANGES }}
      # Allow debugging with tmate
      - name: Setup tmate session
        uses: mxschmitt/action-tmate@v3
        if: ${{ github.event_name == 'workflow_dispatch' && github.event.inputs.debug_enabled == 'true' }}
        with:
          limit-access-to-actor: true