md5.digest(null);
        });
    }

    @Test
    @DisplayName("Should produce consistent hash results")
    void testHashConsistency() {
        // Given
        String input = "Test consistency";
        byte[] data = input.getBytes();

        // When
        MessageDigest md5_1 = Crypto.getMD5();
        MessageDigest md5_2 = Crypto.getMD5();
        byte[] hash1 = md5_1.digest(data);

        JobNotFoundException exception = new JobNotFoundException(message);

        assertEquals(message, exception.getMessage());
        assertEquals(message, exception.getMessage()); // Call twice to verify consistency
        assertEquals(message, exception.getLocalizedMessage());
    }

    @Test
    public void test_toString() {
        // Test toString method
        String message = "Test exception message";

        } catch (Exception e) {
            fail("Should have caught LdapOperationException");
        }
    }

    @Test
    public void test_getMessage_consistency() {
        // Test message consistency across different scenarios
        String message1 = "LDAP bind failed";
        String message2 = "LDAP search failed";
        Exception cause = new Exception("Timeout");

- Some Unformatted - format all and return success.
- Any JBOD inconsistent - return failure
- Some are corrupt (missing format.json) - return failure
- Any unrecognized disks - return failure

Some disks are offline and we have quorum.
-----------------
- Some unformatted - format all and return success,
  treat disks offline as corrupted.
- Any JBOD inconsistent - return failure
- Some are corrupt (missing format.json)

        executor.shutdown();

        // Then - Session should be in consistent state
        // The double-check pattern should prevent inconsistent cleanup
        assertTrue(releaseCount.get() > 0 || acquireCount.get() > 0, "Release and acquire counts should be processed");
    }

    /**
     * Test that trees collection is properly cleared during cleanup.

       * pass.
       *
       * 2. We would probably choose to compare exceptions using == instead of equals() (for
       * consistency with how weak references are cleared). That's a behavior change -- arguably the
       * removal of a feature.
       *
       * Fortunately, exceptions rarely contain references to expensive resources.
       */

    }

    @Test
    void multipleStatsCallsTest() {
        logger.info("[BEGIN] multipleStatsCallsTest");

        // Call stats endpoint multiple times to ensure consistency
        final Map<String, Object> searchBody = new HashMap<>();

        String response1 = checkGetMethod(searchBody, "").asString();
        Integer status1 = JsonPath.from(response1).get("response.status");

</div>

With this feature from **Pydantic v2**, your API documentation is more **precise**, and if you have autogenerated clients and SDKs, they will be more precise too, with a better **developer experience** and consistency. 🎉

## Do not Separate Schemas { #do-not-separate-schemas }

Now, there are some cases where you might want to have the **same schema for input and output**.

	}

	// Clear omitempty fields:
	if j.ObjectV2 != nil && len(j.ObjectV2.PartIndices) > 0 {
		j.ObjectV2.PartIndices = j.ObjectV2.PartIndices[:0]
	}
	o, err = j.UnmarshalMsg(bts)

	// Fix inconsistent x-minio-internal-replication-timestamp by converting to UTC.
	// Fixed in version 2 or later
	if err == nil && j.Type == DeleteType && v < 2 {

            // Both non-null - should be same instance
            assertSame(first, second, "Second getSubject should return same cached instance as first");
        } else {
            fail("Inconsistent behavior: first=" + first + ", second=" + second);
        }

        // Third call should return the same cached Subject instance
        Subject third = auth.getSubject();