* scenarios that don't require complex filter setups.
 */
@ExtendWith(MockitoExtension.class)
class DirFileEntryAdapterIteratorTest {

    @Mock
    private SmbResource mockParent;

    @Mock
    private CloseableIterator<FileEntry> mockDelegate;

    @Mock
    private ResourceFilter mockFilter;

    @Mock
    private FileEntry mockFileEntry1;

    @Mock

class SmbTransportPoolImplTest {

    private SmbTransportPoolImpl pool;

    @Mock
    private CIFSContext ctx;
    @Mock
    private Configuration config;
    @Mock
    private NameServiceClient nameSvc;
    @Mock
    private Credentials creds;
    @Mock
    private Address address;
    @Mock
    private SmbNegotiationResponse negotiationResponse;

    @BeforeEach
    void setUp() {

            assertNotNull(combined);
        }
    }

    @Nested
    @DisplayName("Mock Behavior Verification Tests")
    class MockBehaviorTests {

        @Test
        @DisplayName("Should verify all interface methods can be mocked")
        void testAllMethodsCanBeMocked() {
            // Setup all mock behaviors
            when(mockReferralData.getExpiration()).thenReturn(1000L);

    /**
     * Helper method to create a fully mocked CIFSContext with all necessary dependencies
     */
    private CIFSContext createMockContext() {
        CIFSContext mockContext = mock(CIFSContext.class);
        Configuration mockConfig = mock(Configuration.class);
        NameServiceClient mockNameServiceClient = mock(NameServiceClient.class);
        NetbiosAddress mockHost = mock(NetbiosAddress.class);

_2025-10-09_

 *  Fix: Don't crash when calling `Socket.shutdownOutput()` or `shutdownInput()` on an `SSLSocket`
    on Android API 21 through 23. This method throws an `UnsupportedOperationException`, so we now
    catch that and close the underlying stream instead.

 *  Upgrade: [Okio 3.16.1][okio_3_16_1].


## Version 5.2.0

_2025-10-07_

 *  New: Support [HTTP 101] responses with `Response.socket`. This mechanism is only supported on

      // 2. Client cancels request
      // 3. Server tries to send response on the canceled stream
      // Otherwise, there is no guarantee for the sequence. For example, the server may use the
      // first mocked response to respond to the second request.
      val response = super.dispatch(request)
      responseDequeuedLatches[responseIndex].countDown()
      requestCanceledLatches[responseIndex].await()
      responseIndex++

Vous pouvez en lire davantage dans la [documentation Docker sur les formes shell et exec](https://docs.docker.com/reference/dockerfile/#shell-and-exec-form).

	}
	return lockCopy
}

func (l *localLocker) Close() error {
	return nil
}

// IsOnline - local locker is always online.
func (l *localLocker) IsOnline() bool {
	return true
}

// IsLocal - local locker returns true.
func (l *localLocker) IsLocal() bool {
	return true
}

Você pode ler mais na [documentação do Docker sobre as formas shell e exec](https://docs.docker.com/reference/dockerfile/#shell-and-exec-form).

Isso pode ser bem perceptível ao usar `docker compose`. Veja esta seção de FAQ do Docker Compose para mais detalhes técnicos: [Por que meus serviços demoram 10 segundos para recriar ou parar?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop).

Detaylar için [shell ve exec form için Docker dokümanlarına](https://docs.docker.com/reference/dockerfile/#shell-and-exec-form) bakabilirsiniz.

Bu durum `docker compose` kullanırken oldukça belirgin olabilir. Daha teknik detaylar için şu Docker Compose FAQ bölümüne bakın: [Hizmetlerimin yeniden oluşturulması veya durması neden 10 saniye sürüyor?](https://docs.docker.com/compose/faq/#why-do-my-services-take-10-seconds-to-recreate-or-stop).