The code before yield and the code after yield should be run in the same contextvar
    context, so that request_state_context_var.reset(contextvar_token).

    If they are run in a different context, that raises an error.
    """
    response = client.get("/user")
    assert response.json() == "deadpond"

# Note that "_push" cache configs write to GCS buckets and require
# authentication. If you are not a Googler, source "public_cache" to enable the
# public read-only cache.
# The cache configs are different for MacOS and Linux
if [[ $(uname -s) == "Darwin" ]]; then
  TFCI_BAZEL_COMMON_ARGS="$TFCI_BAZEL_COMMON_ARGS --config tf_public_macos_cache_push"
else

    @Test
    public void testDifferentIpsIndependent() throws Exception {
        // Different IPs should have independent limits
        for (int i = 1; i <= 3; i++) {
            assertTrue(rateLimiter.checkAttempt("user1", "192.168.1." + i));
            rateLimiter.recordFailure("user1", "192.168.1." + i);
        }

        // All different IPs should still be allowed
        for (int i = 1; i <= 3; i++) {

        assertEquals(2, tokensNull.size());
    }

    @Test
    public void testAnalyzeWithDifferentFields() {
        // Test analyze with different field settings
        String text = "test content";
        String lang = "en";

        // Test with different field names
        List<AnalyzeToken> tokensContent = analyzer.analyze(text, "content", lang);
        assertNotNull(tokensContent);

///

### O que é "Montagem" { #what-is-mounting }

"Montagem" significa adicionar uma aplicação completamente "independente" em um path específico, que então cuida de lidar com todos os sub-paths.

Isso é diferente de usar um `APIRouter`, pois uma aplicação montada é completamente independente. A OpenAPI e a documentação da sua aplicação principal não incluirão nada da aplicação montada, etc.

        }
      }
    }
  }

  /**
   * Not checking the CA bit created a vulnerability in old OkHttp releases. It is exploited by
   * triggering different chains to be discovered by the TLS engine and our chain cleaner. In this
   * attack there's several different chains.
   *
   *
   * The victim's gets a non-CA certificate signed by a CA, and pins the CA root and/or
   * intermediate. This is business as usual.
   *

import junit.framework.TestCase;
import junit.framework.TestSuite;
import org.jspecify.annotations.NullUnmarked;

/**
 * Tests our AtomicHelper fallback strategy in AggregateFutureState.
 *
 * <p>On different platforms AggregateFutureState uses different strategies for its core
 * synchronization primitives. The strategies are all implemented as subtypes of AtomicHelper and

        }

        @Test
        @DisplayName("Should handle different buffer positions correctly")
        void testReadBytesWireFormatDifferentPositions() throws SMBProtocolDecodingException {
            byte[] buffer = new byte[1024];

            // Test at different positions
            int[] positions = { 0, 50, 100, 500, 800 };

            for (int position : positions) {

import javax.security.auth.kerberos.KerberosKey;

import jcifs.pac.PACDecodingException;

/**
 * Abstract base class for Kerberos authorization data.
 * This class provides parsing capabilities for different types of Kerberos authorization data.
 */
public abstract class KerberosAuthData {

    /**
     * Default constructor for KerberosAuthData.
     */
    protected KerberosAuthData() {

Vous avez probablement déjà lu que vous pouvez définir un [Code d'état de la réponse](../tutorial/response-status-code.md) par défaut.

Mais dans certains cas, vous devez renvoyer un code d'état différent de celui par défaut.

## Cas d'utilisation { #use-case }

Par exemple, imaginez que vous vouliez renvoyer par défaut un code d'état HTTP « OK » `200`.