Skip to content

fix(http): reject non-finite Doris HTTP timeouts - #239

Open
sol713 wants to merge 1 commit into
apache:masterfrom
sol713:fix/finite-doris-http-timeouts
Open

sol713 wants to merge 1 commit into
apache:masterfrom
sol713:fix/finite-doris-http-timeouts

Conversation

@sol713

@sol713 sol713 commented Oct 9, 2026

Copy link
Copy Markdown

Summary

Reject non-finite Doris HTTP connect/read/total timeout configuration. NaN previously passed validation and disabled the aiohttp total-request deadline. Direct client construction now falls back to existing safe defaults; finite positive values retain the 60-second runtime cap.

Validation

Entirely in Codex cloud: new tests on unchanged upstream had 12 failures and 4 passes; repaired HTTP tests 34 passed. Full suite 1879 passed, 85 skipped; coverage 68.14% and domain floors passed. Ruff, Mypy, Bandit, lockfile, generated catalog, build and clean-wheel checks passed. CI-pinned official MCP conformance: 25/25 passed. A real isolated loopback HTTP server was tested; real Doris integration was not run.

Limitations and AI assistance

Full license-eye scan could not run because its Go dependency download returned HTTP 403. All four changed Apache headers match baseline; no new dependencies. Upstream CI remains required. OpenAI Codex produced analysis, code, tests and this description. No human review or agreement signature is claimed. Draft for maintainer review.

Reject NaN and infinite connect/read/total timeout configuration, and use
safe defaults at the HTTP client boundary when configuration validation
is bypassed. Add configuration, client, and isolated loopback HTTP
regressions showing that NaN cannot disable the total request deadline.

Generated-by: OpenAI Codex (GPT-6)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant