verify(request).size();
        verify(request).getOverrideTimeout();
        verify(request).allowChain(nextRequest);
    }

    @Test
    @DisplayName("Test chaining scenario with multiple requests")
    void testChainingScenario() {
        // Given
        CommonServerMessageBlockRequest thirdRequest = mock(CommonServerMessageBlockRequest.class);

                            } catch (SmbException e) {
                                // Account locked out - this is expected behavior in concurrent scenario
                                blockedAttempts.incrementAndGet();
                                break; // Stop trying if account is locked
                            }

                            if (!allowed) {

            echoResponse.received();
            assertTrue(echoResponse.isReceived());
            assertFalse(echoResponse.isError());
        }

        @Test
        @DisplayName("Should handle error scenario")
        void testErrorScenario() {
            byte[] buffer = new byte[1024];
            int bufferIndex = 64;

            // Write invalid structure size

	}

	res := madmin.HealResultItem{
		Type:     madmin.HealItemBucket,
		Bucket:   bucket,
		SetCount: -1, // explicitly set an invalid value -1, for bucket heal scenario
	}

	for i, err := range errs {
		if err == nil {
			res.Before.Drives = append(res.Before.Drives, healBucketResults[i].Before.Drives...)

You probably won't need to use it directly in your code.

But in case you needed it for an advanced scenario, you can add custom headers:

{* ../../docs_src/handling_errors/tutorial002.py hl[14] *}

## Install custom exception handlers { #install-custom-exception-handlers }

        executor.shutdown();

        assertTrue(exceptions.isEmpty());
        assertEquals(threadCount * operationsPerThread, crawlerContext.getAccessCount());
    }

    /**
     * Test complete workflow scenario
     */
    public void test_completeWorkflow() {
        // Initialize context
        crawlerContext.setSessionId("workflow-session");
        crawlerContext.setStatus(CrawlerStatus.INITIALIZING);

            assertEquals(second, third.next());
            assertEquals(first, second.next());
        }

        @Test
        @DisplayName("Should handle cache replacement in complex scenario")
        void testComplexCacheReplacement() {
            Map<String, DfsReferralDataInternal> cache = new HashMap<>();

            // Create multiple entries
            for (int i = 0; i < 10; i++) {

        assertEquals("30", configMap.get(ConfigName.CONFIG).get("timeout"));
        assertEquals("localhost", configMap.get(ConfigName.CLIENT).get("host"));

        // Test loadConfigParams with complex scenario
        Map<String, Object> targetMap = new HashMap<>();
        targetMap.put("existing", "value");
        String configParam = "new.param=value\nconfig.setting=true";

        }

        @Test
        @DisplayName("Should handle mixed lock operations")
        void testMixedLockOperations() {
            // Simulate a complex scenario with mixed lock operations
            Smb2Lock[] locks = new Smb2Lock[] { new Smb2Lock(0L, 512L, Smb2Lock.SMB2_LOCKFLAG_EXCLUSIVE_LOCK),

### WebIdentityAccessToken (MinIO Extension)

There are situations when identity provider does not provide user claims in `id_token` instead it needs to be retrieved from UserInfo endpoint, this extension is only useful in this scenario. This is rare so use it accordingly depending on your Identity provider implementation. `access_token` is available as part of the OIDC authentication flow similar to `id_token`.

| Params     | Value    |