restored := make(map[string]string)
	restored[xhttp.AmzRestore] = completedRestoreObj(time.Now().UTC().Add(time.Hour)).String()

	restoredExpired := make(map[string]string)
	restoredExpired[xhttp.AmzRestore] = completedRestoreObj(time.Now().UTC().Add(-time.Hour)).String()

	testCases := []struct {
		xlmeta xlMetaV2Object
		uses   bool
	}{
		{ // transitioned object version

        // Verify the method was called
        verify(mockResponse, times(2)).isReceived();
    }

    @Test
    void testReceived() {
        // Call the method
        mockResponse.received();

        // Verify that the method was called
        verify(mockResponse, times(1)).received();
    }

    @Test
    void testClearReceived() {
        // Call the method

        // Test that serialVersionUID is accessible (inherited from parent)
        assertNotNull(exception);

        // Create a new instance to verify it can be created multiple times
        LdapConfigurationException exception2 = new LdapConfigurationException(message);
        assertEquals(exception.getMessage(), exception2.getMessage());
    }

    public void test_toString() {

        // Initialize without container
        emptyGenerator = new EmptyGenerator();

        // Test that destroy method can be called without error
        emptyGenerator.destroy();
        // Call destroy multiple times to ensure it's safe
        emptyGenerator.destroy();
        emptyGenerator.destroy();
    }

    public void test_isAvailable() {
        // Initialize without container
        emptyGenerator = new EmptyGenerator();

Você também pode combinar `dataclasses` com outras anotações de tipo para criar estruturas de dados aninhadas.

Em alguns casos, você ainda pode ter que usar a versão do Pydantic das `dataclasses`. Por exemplo, se você tiver erros com a documentação da API gerada automaticamente.

Nesse caso, você pode simplesmente trocar as `dataclasses` padrão por `pydantic.dataclasses`, que é um substituto direto:

docker-compose -f docker-compose-site2.yaml up -d

./mc ready site1/
./mc ready site2/

for i in $(seq 1 10); do
	# mc admin heal -r --remove when used against a LB endpoint
	# behaves flaky, let this run 10 times before giving up
	./mc admin heal -r --remove --json site1/ 2>&1 >/dev/null
	./mc admin heal -r --remove --json site2/ 2>&1 >/dev/null
done

    }

    @Test
    @DisplayName("Test size returns positive message size")
    void testSizeReturnsPositiveValue() {
        // Given
        int expectedSize = 1024;
        when(request.size()).thenReturn(expectedSize);

        // When
        int result = request.size();

        // Then
        assertEquals(expectedSize, result);
        verify(request, times(1)).size();

      Subscriber that = (Subscriber) obj;
      // Use == so that different equal instances will still receive events.
      // We only guard against the case that the same object is registered
      // multiple times
      return target == that.target && method.equals(that.method);
    }
    return false;
  }

  /**
   * Checks whether {@code method} is thread-safe, as indicated by the presence of the {@link

            assertTrue(cbWithMetrics.getAverageResponseTime() > 0, "Average response time should be tracked");
            assertTrue(cbWithMetrics.getMinResponseTime() > 0, "Min response time should be tracked");
            assertTrue(cbWithMetrics.getMaxResponseTime() > 0, "Max response time should be tracked");
            assertTrue(cbWithMetrics.getP95ResponseTime() > 0, "P95 response time should be tracked");

   * the request completes normally or when it fails due to an exception, in which case [e] should
   * be non-null.
   *
   * If the exchange was canceled or timed out, this will wrap [e] in an exception that provides
   * that additional context. Otherwise [e] is returned as-is.
   */
  internal fun messageDone(
    exchange: Exchange,
    requestDone: Boolean = false,