Agora vamos voltar um pouco e entender o que é isso tudo.

O "fluxo" `password` é uma das formas ("fluxos") definidas no OAuth2 para lidar com segurança e autenticação.

O OAuth2 foi projetado para que o backend ou a API pudesse ser independente do servidor que autentica o usuário.

Mas, neste caso, a mesma aplicação **FastAPI** irá lidar com a API e com a autenticação.

Então, vamos rever de um ponto de vista simplificado:

Now let's go back a bit and understand what is all that.

The `password` "flow" is one of the ways ("flows") defined in OAuth2, to handle security and authentication.

OAuth2 was designed so that the backend or API could be independent of the server that authenticates the user.

But in this case, the same **FastAPI** application will handle the API and the authentication.

So, let's review it from that simplified point of view:

        assertTrue(result.length() > "TransWaitNamedPipeResponse[]".length());
    }

    @Test
    @DisplayName("Multiple instances should be independent")
    void testMultipleInstances() {
        // Arrange
        TransWaitNamedPipeResponse response1 = new TransWaitNamedPipeResponse(mockConfig);

         * The kerberos session key is not accessible via the JGSS API. IBM and
         * Oracle both implement a similar API to make an ExtendedGSSContext
         * available. That API is accessed via reflection to make this independent
         * of the runtime JRE
         */
        if (EXT_GSS_CONTEXT_CLASS == null || INQUIRE_SEC_CONTEXT == null || INQUIRE_TYPE_SESSION_KEY == null) {

Isso foi alterado no FastAPI 0.106.0 com a intenção de não manter recursos enquanto se espera a resposta percorrer a rede.

/// tip | Dica

Além disso, uma tarefa em segundo plano normalmente é um conjunto de lógica independente que deve ser tratado separadamente, com seus próprios recursos (por exemplo, sua própria conexão de banco de dados).

Assim, desta forma você provavelmente terá um código mais limpo.

///

covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's

        for (int i = startIndex + bytesWritten; i < dst.length; i++) {
            assertEquals((byte) (i & 0xFF), dst[i]);
        }
    }

    @Test
    @DisplayName("Test multiple instances independence")
    void testMultipleInstancesIndependence() {
        NtTransQuerySecurityDesc desc1 = new NtTransQuerySecurityDesc(mockConfig, 0x1111, OWNER_SECURITY_INFORMATION);

        // Verify that the configuration was queried for notify buffer size
        verify(mockConfig, atLeastOnce()).getNotifyBufferSize();
    }

    @Test
    @DisplayName("Test multiple instances independence")
    void testMultipleInstancesIndependence() {
        NtTransNotifyChange notify1 = new NtTransNotifyChange(mockConfig, 0x1111, FILE_NOTIFY_CHANGE_FILE_NAME, false);

        // Update second directory cache
        List<SmbFile> files2 = Arrays.asList(mockFile2);
        directoryLeaseManager.updateDirectoryCache(dir2, files2);

        // Verify both caches are independent
        assertTrue(entry1.isComplete());
        assertTrue(entry2.isComplete());
        assertTrue(entry1.hasChild("document.txt"));
        assertFalse(entry1.hasChild("subfolder"));

        return MultipartBody(boundary, type, parts.toImmutableList())
      }
    }

  companion object {
    /**
     * The "mixed" subtype of "multipart" is intended for use when the body parts are independent
     * and need to be bundled in a particular order. Any "multipart" subtypes that an implementation
     * does not recognize must be treated as being of subtype "mixed".
     */
    @JvmField