staleWriters[i] = newBitrotWriter(disk, "", "testbucket", "testobject", erasure.ShardFileSize(test.size), test.algorithm, erasure.ShardSize())
		}

		// test case setup is complete - now call Heal()
		err = erasure.Heal(t.Context(), staleWriters, readers, test.size, nil)
		closeBitrotReaders(readers)
		closeBitrotWriters(staleWriters)
		if err != nil && !test.shouldFail {

        }

        while ((region = availableReceiveRegions.poll()) != null) {
            region.close();
            totalReleased.incrementAndGet();
        }

        log.info("RDMA buffer manager cleanup complete. Total allocated: {}, released: {}", totalAllocated.get(), totalReleased.get());
    }

    /**
     * Close the buffer manager and release all resources
     *
     * @throws Exception if cleanup fails

            });
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should work as complete request-response cycle")
        void testCompleteRequestResponseCycle() {
            // Create request
            Smb2EchoRequest request = new Smb2EchoRequest(mockConfig);

            // Verify request properties

   * Regression test for an edge case where closing response body in the HTTP engine doesn't release
   * the corresponding stream allocation. This test keeps those response bodies alive and reads
   * them after the redirect has completed. This forces a connection to not be reused where it would
   * be otherwise.
   *
   *
   * This test leaks a response body by not closing it.
   *
   * https://github.com/square/okhttp/issues/2409
   */

              docker cp "${sql_file}" "${container_name}":"${sql_file}"
              docker exec -i ${TTY_FLAG} "${container_name}" bash -c "su - omm -c 'gsql -U omm -f ${sql_file}'"
              echo "Database initialization completed."
              break
            fi

            echo "Waiting for database to be ready... (attempt $((retry_count + 1))/$max_retries)"
            sleep 10
            ((++retry_count))
          done

        assertEquals(0, info.getCapacity());
        assertEquals(0, info.getFree());
    }

    @Test
    void testReadDataWireFormat_BufferTooSmall() throws Exception {
        // Test with buffer too small for complete data
        response = new Trans2QueryFSInformationResponse(config, FileSystemInformation.SMB_INFO_ALLOCATION);

        byte[] buffer = new byte[10]; // Too small for SmbInfoAllocation

        // Set dataCount

    void testRunWithZeroIterations() {
        TestLocking t = new TestLocking();
        t.url = "smb://test/file.txt";
        t.numIter = 0; // Zero iterations

        // Should complete immediately
        t.run();
        assertEquals(1, t.numComplete, "numComplete should be incremented");
    }

    @Test
    @DisplayName("TestLocking can be instantiated")
    void testInstantiation() {

# Sicherheit { #security }

Es gibt viele Wege, Sicherheit, Authentifizierung und Autorisierung zu handhaben.

Und normalerweise ist es ein komplexes und „schwieriges“ Thema.

In vielen Frameworks und Systemen erfordert allein die Handhabung von Sicherheit und Authentifizierung viel Aufwand und Code (in vielen Fällen kann er 50 % oder mehr des gesamten geschriebenen Codes ausmachen).

Enviar un body con un request `GET` tiene un comportamiento indefinido en las especificaciones, no obstante, es soportado por FastAPI, solo para casos de uso muy complejos/extremos.

Como no se recomienda, la documentación interactiva con Swagger UI no mostrará la documentación para el body cuando se usa `GET`, y los proxies intermedios podrían no soportarlo.

///

import org.junit.jupiter.api.io.TempDir;

import static org.junit.jupiter.api.Assertions.assertEquals;
import static org.junit.jupiter.api.Assertions.assertTrue;

/**
 * Integration tests for the complete upgrade workflow.
 * These tests verify end-to-end behavior with real strategy implementations.
 */
@DisplayName("Upgrade Workflow Integration")
class UpgradeWorkflowIntegrationTest {

    @TempDir
    Path tempDir;