* get proper ticket caching.
 *
 * Be advised that short/NetBIOS name usage is not supported with this authenticator. Always specify full FQDNs/Realm.
 * This can be a problem if using DFS in it's default configuration as that still returns referrals in short form.
 * See <a href="https://support.microsoft.com/en-us/kb/244380">KB-244380</a> for compatible server configuration.
 * See {@link jcifs.Configuration#isDfsConvertToFQDN()} for a workaround.
 *

What’s changing now:

* 🚫 We’re no longer accepting new community-submitted translation PRs.

* ⏳ Existing open PRs will be reviewed and can still be merged if completed within the next 3 weeks (since July 11 2025).

        assertEquals(8, result); // Structure size (2) + offset (2) + length (4)
        assertNotNull(response.getResults());
        // Bug in implementation: when bufferLength is 0, it still tries to decode at least once
        assertEquals(1, response.getResults().length); // Due to implementation bug
    }

    @Test
    @DisplayName("Test readBytesWireFormat with invalid structure size throws exception")

 *
 *
 * This mainly tracks two locations:
 * - canonical URL path: path component of the URL: this is used to reconstruct URLs to resources and is not adjusted by
 * DFS referrals. (E.g. a resource with a DFS root's parent will still point to the DFS root not the share it's actually
 * located in).
 * - share + uncpath within it: This is the relevant information for most SMB requests. Both are adjusted by DFS

      promoteAndExecute()
    }

  /**
   * The maximum number of requests for each host to execute concurrently. This limits requests by
   * the URL's host name. Note that concurrent requests to a single IP address may still exceed this
   * limit: multiple hostnames may share an IP address or be routed through the same HTTP proxy.
   *
   * If more than [maxRequestsPerHost] requests are in flight when this is invoked, those requests

         * ended up with a magic value that is not compatible with the type of the configured mojo parameter (a string
         * could still be converted by the configurator so we leave those alone). If so, back off to evaluating the
         * expression from properties only.
         */

All the data conversion, validation, documentation, etc. will still work as normally.

That way, we can declare just the differences between the models (with plaintext `password`, with `hashed_password` and without password):

        @CsvSource({ "0, 0, 1024", "1024, 2048, 4096", "9223372036854775807, 9223372036854775807, 2147483647", // Max long values
                "-1, -1, -1", // Negative values (should still create instance)
                "0, 9223372036854775807, 0" // Edge cases
        })
        void testConstructorWithVariousValues(long sourceOffset, long targetOffset, int length) {
            // When

        boolean secondInit = client.isInit.compareAndSet(false, true);
        assertFalse("Second initialization should not occur", secondInit);
        assertTrue("Client should still be initialized", client.isInit.get());
    }

            // Collect keys in iteration order
            List<String> keys = new ArrayList<>();
            modelProps.keySet().forEach(k -> keys.add(k.toString()));

            // Verify order is preserved (first should still be first since it was modified, not re-added)
            assertEquals(3, keys.size());
            assertEquals("first", keys.get(0));
            assertEquals("second", keys.get(1));