return value;
        }
        return defaultValue;
    }

    /**
     * Creates a new DataStoreParams instance with a copy of the current parameters.
     * This provides an independent copy that can be modified without affecting the original.
     *
     * @return a new DataStoreParams instance containing a copy of the current parameters
     */
    public DataStoreParams newInstance() {

        // Second execution
        String result2 = aggregateLogJob.execute();
        assertNotNull(result2);
        assertTrue(result2.contains("Error 2"));

        // Results should be independent
        assertFalse(result1.equals(result2));
    }

    public void test_execute_withEmptyStringException() {
        // Setup mock SearchLogHelper that throws exception with empty message

O "fluxo" da `senha` é um dos caminhos ("fluxos") definidos no OAuth2, para lidar com a segurança e autenticação.

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

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

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

        // Execute on both instances
        dataStore1.store(config, callback, params);
        dataStore2.store(config, callback, params);
        dataStore2.store(config, callback, params);

        // Verify independent operation
        assertEquals(1, store1CallCount.get());
        assertEquals(2, store2CallCount.get());
    }

    // Test implementation of IndexUpdateCallback for testing purposes

        assertNull(pc.getPassword());
        verify(spyAuth, times(1)).getPasswordAsCharArray();
    }

    @Test
    @DisplayName("clone: copies fields and cached subject; instances are independent")
    void testCloneCopiesFieldsAndIndependence() throws Exception {
        // Use configuration-based constructor to also exercise copying of configuration/service fields

            assertEquals(type, iate.getType());
            assertEquals(message, e.getMessage());
        }
    }

    public void test_multipleExceptionInstances() {
        // Test multiple instances are independent
        InvalidAccessTokenException exception1 = new InvalidAccessTokenException("Type1", "Message1");
        InvalidAccessTokenException exception2 = new InvalidAccessTokenException("Type2", "Message2");

        SmbNegotiation anotherNegotiation =
                new SmbNegotiation(anotherRequest, anotherResponse, anotherRequestBuffer, anotherResponseBuffer);

        // Verify the instances are independent
        assertNotSame(negotiation.getRequest(), anotherNegotiation.getRequest());
        assertNotSame(negotiation.getResponse(), anotherNegotiation.getResponse());

El "flujo" `password` es una de las formas ("flujos") definidas en OAuth2, para manejar la seguridad y la autenticación.

OAuth2 fue diseñado para que el backend o la API pudieran ser independientes del servidor que autentica al usuario.

Pero en este caso, la misma aplicación de **FastAPI** manejará la API y la autenticación.

Así que, revisémoslo desde ese punto de vista simplificado:

That's what we'll solve, let's load the model before the requests are handled, but only right before the application starts receiving requests, not while  the code is being loaded.

## Lifespan { #lifespan }

        // Document list size should remain the same
        assertEquals(1, result.getDocumentList().size());
    }

    public void test_multipleBuilds() {
        // Test that each builder creates independent results
        // Create first result with one document
        SearchResult.SearchResultBuilder builder1 = SearchResult.create();
        Map<String, Object> doc1 = new HashMap<>();
        doc1.put("id", "1");