for _, format := range formats {
		if format == nil {
			continue
		}
		// NOTE: This code is specifically needed when migrating version
		// V1 to V2 to V3, in a scenario such as this we only need to handle
		// single sets since we never used to support multiple sets in releases
		// with V1 format version.
		if len(format.Erasure.Sets) > 1 {
			continue
		}

        // Act
        SmbSession result = handle.getSession();

        // Assert
        assertNull(result);
        verify(handle).getSession();
    }

    @Test
    @DisplayName("Scenario: verify interaction order across multiple calls")
    void verifyInteractionOrder() throws Exception {
        // Arrange: stub simple returns
        when(handle.hasCapability(anyInt())).thenReturn(true);

	ProxyRequest                        bool      // only set for GET/HEAD in active-active replication scenario
	ProxyHeaderSet                      bool      // only set for GET/HEAD in active-active replication scenario
	ReplicationRequest                  bool      // true only if replication request
	ReplicationSourceTaggingTimestamp   time.Time // set if MinIOSourceTaggingTimestamp received

        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);

En muchos casos no es muy obvio cómo las variables de entorno serían útiles y aplicables de inmediato. Pero siguen apareciendo en muchos escenarios diferentes cuando estás desarrollando, así que es bueno conocerlas.

            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

	// Initialize heal result info
	res = madmin.HealResultItem{
		Type:      madmin.HealItemBucket,
		Bucket:    bucket,
		DiskCount: len(localDrives),
		SetCount:  -1, // explicitly set an invalid value -1, for bucket heal scenario
	}

	// mutate only if not a dry-run
	if opts.DryRun {
		return res, nil
	}

	for i := range beforeState {
		res.Before.Drives = append(res.Before.Drives, madmin.HealDriveInfo{
			UUID:     "",

### Bug or Regression

- An inefficient lock in EndpointSlice controller metrics cache has been reworked. Network programming latency may be significantly reduced in certain scenarios, especially in clusters with a large number of Services. ([#107167](https://github.com/kubernetes/kubernetes/pull/107167), [@robscott](https://github.com/robscott)) [SIG Apps and Network]

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

                            if (!allowed) {

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 }