assertNull(unwrapped);
        }
    }

    @Nested
    @DisplayName("Exception handling tests")
    class ExceptionHandlingTests {

        @Test
        @DisplayName("doEnum rethrows CIFSException when not UnknownHostException")

Before FastAPI 0.106.0, raising exceptions after `yield` was not possible, the exit code in dependencies with `yield` was executed *after* the response was sent, so [Exception Handlers](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} would have already run.

 * It supports password-protected PDFs and can extract embedded documents and annotations.
 *
 * <p>The extractor runs text extraction in a separate thread with a configurable timeout
 * to prevent hanging on problematic PDF files. It also extracts metadata from the PDF
 * document and includes it in the extraction result.
 *
 * <p>Features:
 * <ul>
 *   <li>Text extraction from PDF pages</li>

The main constraint to consider is that there has to be a **single** component handling the **port** in the **public IP**. And then it has to have a way to **transmit** the communication to the replicated **processes/workers**.

Here are some possible combinations and strategies:

* **Uvicorn** with `--workers`

        ace.flags = 0xF0 | ACE.FLAGS_CONTAINER_INHERIT;
        assertEquals("This folder and subfolders", ace.getApplyToText());
    }

    @Test
    @DisplayName("Test null SID handling in toString")
    void testToStringWithNullSID() {
        ace.allow = true;
        ace.access = 0x001200A9;
        ace.flags = 0x00;
        ace.sid = null;

import org.codelibs.fess.mylasta.direction.FessConfig;
import org.codelibs.fess.util.ComponentUtil;
import org.codelibs.jcifs.smb.SID;

import jakarta.annotation.Resource;

/**
 * Helper class for handling permission-related operations in Fess.
 * Provides functionality to encode/decode permission strings and extract
 * role type information from various file system protocols (SMB, file, FTP).
 */
public class PermissionHelper {

import org.codelibs.core.exception.ResourceNotFoundRuntimeException;
import org.codelibs.core.jar.JarFileUtil;
import org.codelibs.core.net.URLUtil;

/**
 * Utility class for resource handling.
 *
 * @author higa
 */
public abstract class ResourceUtil {

    /**
     * Do not instantiate.
     */
    protected ResourceUtil() {
    }

    /**
     * Returns the resource path.

            assertNotNull(result);
            assertTrue(result.contains("SmbInfoAllocation")); // Note: toString() uses this name
        }
    }

    @Nested
    @DisplayName("Edge Cases and Error Handling")
    class EdgeCasesTests {

        @Test
        @DisplayName("Should handle null buffer in decode")
        void testNullBuffer() {
            FileFsSizeInformation info = new FileFsSizeInformation();

 *   <li><strong>Comment Preservation</strong>: Preserves XML comments and processing instructions</li>
 *   <li><strong>Line Separator Handling</strong>: Uses system-appropriate line separators</li>
 * </ul>
 */
public abstract class AbstractUpgradeGoal implements Goal {

    private final StrategyOrchestrator orchestrator;

    @Inject

Antes de FastAPI 0.106.0, elevar excepciones después de `yield` no era posible, el código de salida en dependencias con `yield` se ejecutaba después de que la response era enviada, por lo que [Manejadores de Excepciones](../tutorial/handling-errors.md#install-custom-exception-handlers){.internal-link target=_blank} ya habrían corrido.