assertNotNull(suggestItem);
        assertEquals(word, suggestItem.getText());
        assertEquals(boost, suggestItem.getUserBoost(), 0.001f);
        // The queryFreq and docFreq might be handled differently by SuggestItem
        assertTrue(suggestItem.getQueryFreq() >= 0);
        assertTrue(suggestItem.getDocFreq() >= 0);

        // Check readings
        String[][] itemReadings = suggestItem.getReadings();

        VersionRange mergedRange = range1.restrict(range2);
        // TODO current policy is to retain the original version - is this correct, do we need strategies or is that
        // handled elsewhere?
        //        assertEquals( "1.1", mergedRange.getRecommendedVersion().toString(), CHECK_VERSION_RECOMMENDATION );

   *       you can decrease the number of tasks from 15 and 10, killing off the final 5 tasks, and
   *       {@code consistentHash} will handle it. If, however, you are dividing traffic among
   *       servers {@code alpha}, {@code bravo}, and {@code charlie} and you occasionally need to

container is built.
     * Turnkey Deployments (Deployment API (Beta) in the Extensions API group)
automate deployment and rolling updates of applications, specified
declaratively. It handles versioning, multiple simultaneous rollouts,
aggregating status across all pods, maintaining application availability, and
rollback.
  * <strong>Automated cluster management: </strong>

  </ciManagement>
  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
    <resources>
      <resource>
        <directory>../..</directory>

  <modules>
    <module>guava</module>
    <module>guava-bom</module>
    <module>guava-gwt</module>
    <module>guava-testlib</module>
    <module>guava-tests</module>
  </modules>
  <build>
    <!-- Handle where Guava deviates from Maven defaults -->
    <sourceDirectory>src</sourceDirectory>
    <testSourceDirectory>test</testSourceDirectory>
    <resources>
      <resource>
        <directory>..</directory>

    void testReadMethodsWithNullBuffer() {
        trans2QueryFSInfo = new Trans2QueryFSInformation(config, FileSystemInformation.SMB_INFO_ALLOCATION);

        // All read methods should handle null buffer gracefully by returning 0
        assertEquals(0, trans2QueryFSInfo.readSetupWireFormat(null, 0, 0));
        assertEquals(0, trans2QueryFSInfo.readParametersWireFormat(null, 0, 0));

    @DisplayName("Test with null buffer in read methods")
    void testReadMethodsWithNullBuffer() {
        trans2SetFileInfo = new Trans2SetFileInformation(config, TEST_FID, mockFileInfo);

        // All read methods should handle null buffer gracefully
        assertEquals(0, trans2SetFileInfo.readSetupWireFormat(null, 0, 0));
        assertEquals(0, trans2SetFileInfo.readParametersWireFormat(null, 0, 0));

        ConfigurableRule rule = new ConfigurableRule();
        rule.setRuleId("nullTest");
        rule.setResponseProcessor(new TestResponseProcessor("nullProcessor"));

        // Should handle null gracefully
        assertFalse(rule.match(null));
    }

    /**
     * Test Rule with null rule ID
     */
    public void test_nullRuleId() {

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

    @Test
    @DisplayName("Test decode handles SACL offset correctly")
    void testDecodeHandlesSaclOffset() throws SMBProtocolDecodingException {
        // Prepare buffer with SACL offset (should be ignored)
        testBuffer[0] = 0x01; // revision