}
        // We reschedule ourselves with a lock held for two reasons. 1. we want to make sure that
        // cancel calls cancel on the correct future. 2. we want to make sure that the assignment
        // to currentFuture doesn't race with itself so that currentFuture is assigned in the
        // correct order.
        Throwable scheduleFailure = null;
        Cancellable toReturn;
        lock.lock();
        try {

        assertTrue(exception instanceof Exception);
        assertTrue(exception instanceof Throwable);
    }

    public void test_serialization() {
        // Test that the exception has the correct serialVersionUID field
        ScriptEngineException exception = new ScriptEngineException("Serialization test");

        // Verify the exception can be created and basic properties work
        assertNotNull(exception);

        assertTrue(ex.getMessage().contains("failed"));
        verify(session).treeConnectLogon();
    }

    // Happy path: getSmbTree returns a tree and receives correct args
    @Test
    @DisplayName("getSmbTree returns tree and captures arguments")
    void getSmbTree_happy() {
        when(session.getSmbTree(anyString(), anyString())).thenReturn(tree);

constraints.LuhnCheck.message = Il checksum Luhn Modulo 11 di {value} non è corretto.
constraints.Mod10Check.message = Il checksum Modulo 10 di {value} non è corretto.
constraints.Mod11Check.message = Il checksum Modulo 11 di {value} non è corretto.
constraints.ModCheck.message = Il checksum {modType} di {value} non è corretto.
constraints.NotBlank.message = {item} non può essere vuoto.

You can have sub-dependencies and "trees" of sub-dependencies of any size and shape, and any or all of them can use `yield`.

**FastAPI** will make sure that the "exit code" in each dependency with `yield` is run in the correct order.

For example, `dependency_c` can have a dependency on `dependency_b`, and `dependency_b` on `dependency_a`:

{* ../../docs_src/dependencies/tutorial008_an_py39.py hl[6,14,22] *}

And all of them can use `yield`.

		{
			authString:    "NoV2Prefix",
			expectedError: ErrSignatureVersionNotSupported,
		},
		// Test case - 3.
		// Test case with missing parts in the Auth string.
		// below is the correct format of V2 Authorization header.
		// Authorization = "AWS" + " " + AWSAccessKeyId + ":" + Signature
		{
			authString:    signV2Algorithm,
			expectedError: ErrMissingFields,
		},
		// Test case - 4.

        }
    }

    @Nested
    @DisplayName("Size Calculation Tests")
    class SizeTests {

        @ParameterizedTest
        @DisplayName("Should calculate correct size for various path lengths")
        @CsvSource({ "'', 4", "'a', 6", "'\\\\', 8", "'\\\\server', 20", "'\\\\server\\share', 32", "'\\\\server\\share\\path', 42",

            int terminationPos = Strings.findUNITermination(bufferWithTermination, 0, bufferWithTermination.length);

            // Then
            assertEquals(stringBytes.length, terminationPos, "Should find termination at correct position");
        }

        @Test
        @DisplayName("findUNITermination should throw exception when termination not found")
        void testFindUNITerminationNotFound() {
            // Given

# Separación de Esquemas OpenAPI para Entrada y Salida o No

Al usar **Pydantic v2**, el OpenAPI generado es un poco más exacto y **correcto** que antes. 😎

De hecho, en algunos casos, incluso tendrá **dos JSON Schemas** en OpenAPI para el mismo modelo Pydantic, para entrada y salida, dependiendo de si tienen **valores por defecto**.

Veamos cómo funciona eso y cómo cambiarlo si necesitas hacerlo.

## Modelos Pydantic para Entrada y Salida

        StackTraceElement[] stackTrace = exception.getStackTrace();
        assertEquals(0, stackTrace.length);
    }

    public void test_serialization() {
        // Test that the exception has correct serialVersionUID
        String parentUrl = "http://example.com/parent";
        String url = "http://example.com/child";
        ContentNotFoundException exception = new ContentNotFoundException(parentUrl, url);