class VersionComparisonTests {

        @Test
        @DisplayName("should compare versions correctly")
        void shouldCompareVersionsCorrectly() {
            // Based on the actual implementation, it only handles specific cases
            assertTrue(ModelVersionUtils.isVersionGreaterOrEqual("4.1.0", "4.1.0"));
            assertFalse(ModelVersionUtils.isVersionGreaterOrEqual("4.0.0", "4.1.0"));

///

/// tip

Instead of returning a `StreamingResponse` directly, you should probably follow the style in [Stream Data](./stream-data.md), it's much more convenient and handles cancellation behind the scenes for you.

If you are streaming JSON Lines, follow the [Stream JSON Lines](../tutorial/stream-json-lines.md) tutorial.

///

### `FileResponse` { #fileresponse }

	TypeFifo    = '6' // FIFO node

	// Type '7' is reserved.
	TypeCont = '7'

	// Type 'x' is used by the PAX format to store key-value records that
	// are only relevant to the next file.
	// This package transparently handles these types.
	TypeXHeader = 'x'

	// Type 'g' is used by the PAX format to store key-value records that
	// are relevant to all subsequent files.
	// This package only supports parsing and composing such headers,

        assertEquals("q", inputs2[1]);
        assertEquals("r", inputs2[2]);
    }

    @Test
    public void test_defensiveCopy_nullArrays() {
        // Test that defensive copy handles null arrays correctly
        CharMappingItem item1 = new CharMappingItem(1L, new String[] { "a" }, "output");

        // Set to null
        item1.setNewInputs(null);

        // Should return null, not crash

        assertEquals(4, attemptCount.get());
    }

    /**
     * Test: Null safety in connect() when targetIndices is null
     * Verifies that connect() handles null targetIndices gracefully
     */
    @Test
    public void testConnectWithNullTargetIndices() {
        final AdminClient mockAdminClient = mock(AdminClient.class);

Si quieres capturar excepciones y crear un response personalizado en base a eso, crea un [Manejador de Excepciones Personalizado](../handling-errors.md#install-custom-exception-handlers).

## Dependencias con `yield` y `except` { #dependencies-with-yield-and-except }

在 FastAPI 0.106.0 之前，`yield` 之后抛出异常是不可行的，因为带 `yield` 的依赖项中的退出代码会在响应发送之后才执行，此时[异常处理器](../tutorial/handling-errors.md#install-custom-exception-handlers)已经运行完毕。

之所以这样设计，主要是为了允许在后台任务中继续使用依赖项通过 `yield`“产出”的对象，因为退出代码会在后台任务完成之后才执行。

在 FastAPI 0.106.0 中，这一行为被修改，目的是避免在等待响应通过网络传输时一直占用资源。

/// tip | 提示

另外，后台任务通常是一段独立的逻辑，应该单独处理，并使用它自己的资源（例如它自己的数据库连接）。

 *   <li>MIME type detection</li>
 *   <li>Handling of large files through temporary file storage</li>
 *   <li>Object metadata retrieval</li>
 *   <li>Directory listing capabilities</li>
 * </ul>
 *
 * <p>The client handles timeout management for access operations and includes proper
 * resource cleanup mechanisms.
 */
public class GcsClient extends AbstractCrawlerClient {

import jcifs.CIFSContext;
import jcifs.CIFSException;
import jcifs.dcerpc.ndr.NdrBuffer;
import jcifs.dcerpc.ndr.NdrException;

/**
 * Abstract base class for DCE/RPC communication handles.
 * This class provides the foundation for DCE/RPC client communication.
 */
public abstract class DcerpcHandle implements DcerpcConstants, AutoCloseable {

    /*
     * Bindings are in the form:

        inputList.clear();
        assertEquals(2, notifications.size());

        // Try to modify returned list - behavior depends on implementation
        // This tests that the implementation properly handles list modifications
        try {
            notifications.clear();
            // If this succeeds, the implementation allows modification
            assertTrue(notifications.isEmpty());