import org.mockito.Mock;
import org.mockito.MockedStatic;
import org.mockito.junit.jupiter.MockitoExtension;

import jcifs.CIFSException;
import jcifs.spnego.NegTokenInit;

@ExtendWith(MockitoExtension.class)
class Kerb5ContextTest {

    @Mock
    private GSSManager gssManager;

    @Mock
    private GSSContext gssContext;

    @Mock
    private GSSName serviceName;

    @Mock

            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 utiliser <a href="https://www.docker.com/" class="external-link" target="_blank">**Docker**</a> pour le déploiement. Il présente plusieurs avantages comme la sécurité, la réplicabilité, la simplicité de développement, etc.

Si vous utilisez Docker, vous pouvez utiliser l'image Docker officielle :

	}
	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
}

// You should have received a copy of the GNU Affero General Public License
// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package dsync

import "context"

// NetLocker is dsync compatible locker interface.
type NetLocker interface {
	// Do read lock for given LockArgs.  It should return
	// * a boolean to indicate success/failure of the operation
	// * an error on failure of lock request operation.

Você pode ler mais na <a href="https://docs.docker.com/reference/dockerfile/#shell-and-exec-form" class="external-link" target="_blank">documentação do Docker sobre as formas shell e exec</a>.

## コンテナ・イメージ

Dockerは、**コンテナ・イメージ**と**コンテナ**を作成・管理するための主要なツールの1つです。

そして、DockerにはDockerイメージ（コンテナ）を共有する<a href="https://hub.docker.com/" class="external-link" target="_blank">Docker Hub</a>というものがあります。

Docker Hubは 多くのツールや環境、データベース、アプリケーションに対応している予め作成された**公式のコンテナ・イメージ**をパブリックに提供しています。

例えば、公式イメージの1つに<a href="https://hub.docker.com/_/python" class="external-link" target="_blank">Python Image</a>があります。