*
   * <p>This deliberately avoids all nameservice lookups (e.g. no DNS).
   *
   * <p>This method accepts non-ASCII digits, for example {@code "１９２.１６８.０.１"} (those are fullwidth
   * characters). That is consistent with {@link InetAddress}, but not with various RFCs. If you
   * want to accept ASCII digits only, you can use something like {@code
   * CharMatcher.ascii().matchesAllOf(ipString)}.
   *

			t.Errorf("Test case %d, expect to pass but failed. Wanted modTime: %s, got modTime: %s\n", i+1, testCase.time, ctime)
		}
	}
}

// TestListOnlineDisks - checks if listOnlineDisks and outDatedDisks
// are consistent with each other.
func TestListOnlineDisks(t *testing.T) {
	if runtime.GOOS == globalWindowsOSName {
		t.Skip()
	}

	ctx, cancel := context.WithCancel(t.Context())
	defer cancel()

    4.2.2.
 *  Fix: Drop partial support for HTTP/1.0. Previously OkHttp would send
    `HTTP/1.0` on connections after seeing a response with `HTTP/1.0`. The fixed
    behavior is consistent with Firefox and Chrome.
 *  Fix: Allow a body in `OPTIONS` requests.
 *  Fix: Don't percent-encode non-ASCII characters in URL fragments.
 *  Fix: Handle null fragments.

 * <ul>
 *   <li>Preventing duplicate repositories that could cause confusion</li>
 *   <li>Rejecting null repository entries that would cause failures</li>
 *   <li>Maintaining consistent repository ordering for reproducible builds</li>
 * </ul>
 *
 * @since 4.0.0
 * @see RemoteRepository
 * @see Session#getRemoteRepositories()
 */
@Experimental
@Immutable

            assertFalse("validateCalled should be false as exception thrown before flag set", extractor.isValidateCalled());
        }
    }

    /**
     * Test that validateInputStream is consistent across multiple calls.
     */
    public void test_validateInputStream_consistentAcrossMultipleCalls() {
        final InputStream in1 = new ByteArrayInputStream("data1".getBytes());

</div>

Con esta funcionalidad de **Pydantic v2**, la documentación de tu API es más **precisa**, y si tienes clientes y SDKs autogenerados, también serán más precisos, con una mejor **experiencia para desarrolladores** y consistencia. 🎉

## No Separar Esquemas { #do-not-separate-schemas }

Ahora, hay algunos casos donde podrías querer tener el **mismo esquema para entrada y salida**.

Com esse recurso do **Pydantic v2**, sua documentação da API fica mais **precisa**, e se você tiver clientes e SDKs gerados automaticamente, eles serão mais precisos também, proporcionando uma melhor **experiência para desenvolvedores** e consistência. 🎉

## Não Separe Schemas { #do-not-separate-schemas }

Agora, há alguns casos em que você pode querer ter o **mesmo esquema para entrada e saída**.

generates the identity as a public key. This also // makes this function consistent with crypto/elliptic.GenerateKey. key[1] ^= 0x42 // Mask off any excess bits if the size of the underlying field is not a // whole number of bytes, which is only the case for P-521. if c.curve == p521 && c.N[0]&0b1111_1110 == 0 { key[0] &= 0b0000_0001 } privateKey, err := NewPrivateKey(c, key) if err != nil { continue } // A "Pairwise Consistency Test" makes no sense if we just generated the // public key from an ephemeral...

            this.cachedSubject = s;
            return this.cachedSubject;
        } catch (LoginException e) {
            log.error("Failed to create login context", e);
            // Cache null to ensure consistent behavior across calls
            this.cachedSubject = null;
            return null;
        }
    }

    /**
     * {@inheritDoc}
     *
     * @see jcifs.smb.SmbRenewableCredentials#renew()

   * without grabbing the lock.
   *
   * <p>To update this field correctly the lock must be held to guarantee that the state is
   * consistent.
   */
  private volatile StateSnapshot snapshot = new StateSnapshot(NEW);

  /** Constructor for use by subclasses. */
  protected AbstractService() {}

  /**