*/
    @ParameterizedTest
    @MethodSource("provideErrorClassAndCodeForGetErrorString")
    @DisplayName("getErrorString should return correct messages for all defined error classes and codes")
    void testGetErrorString(int errorClass, int errorCode, String expectedMessage) {
        assertEquals(expectedMessage, NbtException.getErrorString(errorClass, errorCode),

Let's look at how we can make that work.

## pytest.mark.anyio { #pytest-mark-anyio }

        }
        // 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 {

For Spanish, as I'm a native speaker and it's a language close to me, I will give it a final review myself and in most cases tweak the PR a bit before merging it.

For the other languages, confirm that:

* The title is correct following the instructions above.
* It has the labels `lang-all` and `lang-{lang code}`.
* The PR changes only one Markdown file adding a translation.

Você também pode declarar parâmetros de **corpo**, **rota** e **consulta**, ao mesmo tempo.

O **FastAPI** irá reconhecer cada um deles e retirar a informação do local correto.

{* ../../docs_src/body/tutorial004.py hl[18] *}

Os parâmetros da função serão reconhecidos conforme abaixo:

* Se o parâmetro também é declarado na **rota**, será utilizado como um parâmetro de rota.

        // Execute with second engine
        Object result2 = scriptExecutor.execute("type2", "script for engine2");
        assertEquals("engine2:processed: script for engine2", result2);

        // Verify correct engine was called each time
        assertEquals("script for engine1", engine1.getLastScript());
        assertEquals("script for engine2", engine2.getLastScript());
    }

				pop := dirStack[len(dirStack)-1]
				select {
				case <-ctx.Done():
					return ctx.Err()
				case out <- metaCacheEntry{name: pop}:
				}
				if opts.Recursive {
					// Scan folder we found. Should be in correct sort order where we are.
					err := scanDir(pop)
					if err != nil {
						if errors.Is(err, context.Canceled) {
							return err
						}
						internalLogIf(ctx, err)
					}
				}

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

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`.