Bug: HttpWaitStrategy ignores response predicates for accepted HTTP error statuses

Aberta Para iniciantes
#1,143 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@PranavMulakala já está trabalhando nisso.

Desde 23/10/2026.

  • #1144 de @PranavMulakala — aberto

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
85/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
testing

Direção de pesquisa

Comece em testcontainers/core/wait_strategies.py em HttpWaitStrategy._handle_http_error(), que retorna True sem verificar _response_predicate. Leia _check_response() para ver a avaliação normal do predicado. Execute o script de reprodução da issue para ver o ready falso e depois edite o ramo de erro para avaliar o predicado. Concluído significa que o script gera TimeoutError.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

Describe the bug

HttpWaitStrategy.for_response_predicate() is not evaluated when an HTTP endpoint returns an explicitly accepted error status, such as 404 or 503. The strategy reports ready even when the response body does not match the predicate.

This affects both for_status_code(...) and for_status_code_matching(...). HTTP 200 responses do evaluate the body predicate. A caller that deliberately accepts an error status still needs the additional body condition to pass; accepting the status should not bypass that condition.

Found while testing HTTP readiness behavior on main at 6146aa1170f415fcc825ed9bddc4eacbeb937a12 (package version 4.15.0). I searched issues and PRs for HttpWaitStrategy, for_response_predicate, response predicate, and HTTPError and did not find this behavior reported. The HTTPError resource-cleanup work in #1115 is related code but a different problem.

Reproduction

This endpoint always returns 503 with body starting. The status is deliberately accepted, but the body predicate requires ready.

"""Reproduce a false-positive HTTP readiness result (requires Docker)."""
from testcontainers.core.container import DockerContainer
from testcontainers.core.wait_strategies import HttpWaitStrategy

server = """
from http.server import BaseHTTPRequestHandler, HTTPServer

class Handler(BaseHTTPRequestHandler):
    def do_GET(self):
        self.send_response(503)
        self.end_headers()
        self.wfile.write(b"starting")

HTTPServer(("0.0.0.0", 8080), Handler).serve_forever()
"""
strategy = (
    HttpWaitStrategy(8080)
    .for_status_code(503)
    .for_response_predicate(lambda body: body == "ready")
    .with_startup_timeout(2)
    .with_poll_interval(0.1)
)
try:
    with (
        DockerContainer("python:3.12-alpine")
        .with_exposed_ports(8080)
        .with_command(["python", "-u", "-c", server])
        .waiting_for(strategy)
    ):
        raise AssertionError("BUG: marked ready even though the body is always 'starting'")
except TimeoutError:
    print("Correct: the body never matched, so readiness timed out.")

Expected behavior

The wait should continue polling and raise TimeoutError because the body never matches.

Actual behavior

The context manager enters immediately after the first HTTP response; the assertion fails. In a second reproduction, an endpoint returning starting on request 1 and ready on request 2 receives only one request before the wait finishes.

Root cause and proposed fix

urlopen() raises HTTPError for error statuses. _handle_http_error() accepts the status and returns True without evaluating _response_predicate. The normal response path in _check_response() does evaluate it.

Evaluate the body predicate for accepted HTTP errors while the existing with e: block still owns the response. This preserves status-only waits and response cleanup.

Runtime environment

  • macOS / Apple silicon; Colima Docker runtime
  • Regression tests reproduced on Python 3.12.14
  • Patch validated on Python 3.10.22, 3.12.14, 3.13.17, and 3.14.9
  • Real HTTP server in python:3.12-alpine
Linguagem predominante
Python
Estrelas
2.3k
Forks
395
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de testcontainers/testcontainers-python

Todas as issues de testcontainers/testcontainers-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.