deferred.resolve(new SuggestResponse("", 0, Collections.emptyList(), 0, null));

        assertTrue("Then callback should complete", latch.await(10, TimeUnit.SECONDS));
        Thread.sleep(100); // Wait a bit to ensure error callback isn't called
        assertEquals("Then callback should be invoked", 1, thenCount.get());
        assertEquals("Error callback should not be invoked", 0, errorCount.get());
    }

    @Test

While there are competing ways to represent absence (`Optional`, "Null Object" pattern, method overloads),
it is unlikely that we'll be able to remove `null` entirely.

After migrating to Java 8, we can use pluggable type checkers to ensure that our annotations are consistent, 
and there are no missing null checks.

## Decision

Use "NullAway" in JSpecify mode to check for null-related errors in Java code.

    withContext(Dispatchers.IO) {
      fileSystem.write(outputFile) {
        importResults.writeOut(this)
      }
    }

  /**
   * These assertions ensure the [PublicSuffixDatabase] remains correct. The specification is
   * very flexible regarding wildcard rules, but this flexibility is not something currently used

 *  **Fix: Lazily initialize the response cache.** This avoids strict mode
    warnings when initializing OkHttp on Android‘s main thread.

 *  **Fix: Disable ALPN on Android 4.4.** That release of the feature was
    unstable and prone to native crashes in the underlying OpenSSL code.
 *  Fix: Don't send both `If-None-Match` and `If-Modified-Since` cache headers
    when both are applicable.

 documentation for details on file names, formats, and so on.

 During Maven initialization, Maven tweaks default root logging level to match CLI verbosity choice. Since such feature isn't available
 in SLF4J API, logging implementation specific extensions need to be added into Maven to support these CLI options: see

        synchronized (messagesLock) {
            if (messages != null && messages.size() > maxMessages) {
                int start = messages.size() - maxMessages;
                // Ensure trimmed history starts with a user message, not an assistant message
                if (start < messages.size() && ChatMessage.ROLE_ASSISTANT.equals(messages.get(start).getRole())) {
                    start = Math.max(0, start - 1);

        assertEquals("Error 1", exception1.getMessage());
        assertEquals("Error 2", exception2.getMessage());
        assertEquals("Error 3", exception3.getMessage());

        // Ensure they are different instances
        assertNotSame(exception1, exception2);
        assertNotSame(exception2, exception3);
        assertNotSame(exception1, exception3);
    }

    @Test

import org.mockito.quality.Strictness;

/**
 * Tests for SmbTreeHandle interface.
 * This test class uses Mockito to create a mock implementation of the SmbTreeHandle interface.
 * Each method of the interface is tested to ensure it behaves as expected.
 */
@ExtendWith(MockitoExtension.class)
@MockitoSettings(strictness = Strictness.LENIENT)
class SmbTreeHandleTest {

    @Mock
    private SmbTreeHandle smbTreeHandle;

    @Mock

        loadBalancer.setStrategy(LoadBalancingStrategy.WEIGHTED_RANDOM);
        when(mockChannelManager.getHealthyChannels()).thenReturn(Arrays.asList(channel1, channel2));

        // Test multiple selections to ensure it works
        for (int i = 0; i < 10; i++) {
            ChannelInfo selected = loadBalancer.selectChannel(mockMessage);
            assertTrue(Arrays.asList(channel1, channel2).contains(selected));
        }
    }

    }

    /**
     * Parameterized test for the {@link DosFileFilter#accept(SmbFile)} method.
     * This test covers various combinations of file attributes and filter attributes
     * to ensure the bitwise logic is correctly implemented.
     *
     * @param filterAttributes The attributes set for the filter.
     * @param fileAttributes The attributes of the mock file.