String result1 = provider1.toString();
        String result2 = provider2.toString();

        // Both should have the same format structure
        assertTrue(result1.startsWith("FessUserTimeZoneProcessProvider:{"));
        assertTrue(result2.startsWith("FessUserTimeZoneProcessProvider:{"));

        // But different hash codes

        final int start = bufferIndex;
        final int structureSize = SMBUtil.readInt2(buffer, bufferIndex);
        if (structureSize != 16) {
            throw new SMBProtocolDecodingException("Structure size is not 16");
        }

        this.shareType = buffer[bufferIndex + 2];
        bufferIndex += 4;
        this.shareFlags = SMBUtil.readInt4(buffer, bufferIndex);
        bufferIndex += 4;

        // StructureSize (2 bytes) - must be 44
        this.structureSize = SMBUtil.readInt2(buffer, bufferIndex);
        if (this.structureSize != 44) {
            throw new SMBProtocolDecodingException("Invalid lease break structure size: " + this.structureSize);
        }
        bufferIndex += 2;

        // Reserved (2 bytes)
        bufferIndex += 2;

        // Flags (4 bytes)

    @Override
    public int size() {
        // Context header: 16 bytes
        // Name: 4 bytes ("RqLs")
        // Padding: 4 bytes (to align data to 8-byte boundary)
        // Data: 32 bytes (lease V1 structure)
        return 16 + 4 + 4 + 32;
    }

    @Override
    public int encode(byte[] dst, int dstIndex) {
        int start = dstIndex;

        // Write context header

import org.codelibs.fess.crawler.exception.CrawlerSystemException;
import org.codelibs.fess.crawler.interval.IntervalController;

/**
 * An abstract base class for implementing {@link IntervalController}.
 * Provides a common structure for handling delays at different stages of the crawling process.
 * It encapsulates the delay logic and exception handling, allowing subclasses to focus on
 * defining the specific delay behavior for each stage.
 *
 * <p>

        assertEquals(-1, ((QueryRescorerBuilder) result).windowSize().intValue());
    }

    public void test_evaluate_withComplexParams() {
        // Test with complex parameter map including nested structures
        final String testModelName = "complex_model";
        final int testWindowSize = 200;

        ComponentUtil.setFessConfig(new FessConfig.SimpleImpl() {
            @Override

        dstIndex += 4;

        // Padding to align data to 8-byte boundary
        dstIndex += 4;

        // Write durable handle V2 request data (32 bytes total)
        // MS-SMB2 2.2.13.2.4 structure:
        SMBUtil.writeInt4((int) getTimeoutFor100Ns(), dst, dstIndex); // Timeout (4 bytes in 100-ns intervals)
        dstIndex += 4;

        SMBUtil.writeInt4(flags, dst, dstIndex); // Flags (4 bytes)

## Example { #example }

For a simple example, let's consider a file structure similar to the one described in [Bigger Applications](../tutorial/bigger-applications.md){.internal-link target=_blank} and [Testing](../tutorial/testing.md){.internal-link target=_blank}:

```
.
├── app
│   ├── __init__.py

  <span style="background-color:#009485"><font color="#D3D7CF"> FastAPI </font></span>  Starting development server 🚀

             Searching for package file structure from directories with
             <font color="#3465A4">__init__.py</font> files
             Importing from <font color="#75507B">/home/user/code/</font><font color="#AD7FA8">awesomeapp</font>

        assertTrue(exception instanceof java.io.Serializable);
    }

    public void test_getMessage_withComplexCause() {
        // Test getMessage behavior with complex cause structure
        final Exception innerCause = new NullPointerException("NPE occurred");
        final Exception outerCause = new IllegalStateException("State error", innerCause);