apache / apache/iotdb-client-rust

connect_timeout is applied per resolved address, not per endpoint

Abierto
#7 0 comentarios 0 reacciones 0 asignados Ver en GitHub
bug
Lenguaje dominante
Rust
Estrellas
1
Forks
0
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

`connect_stream` applies `connect_timeout` **per resolved address**, not per endpoint, contradicting the doc comment ("TCP connect timeout per endpoint attempt"). A hostname resolving to two addresses multiplies every bound: measured 2.0011s for two blackhole addresses at a 1s timeout.

Fix: give `connect_stream` a single total deadline across all resolved addresses, so the timeout bounds the endpoint attempt as documented.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Línea de trabajo

Start by reading connect_stream and its connect_timeout doc comment, then reproduce the two-address case described in the issue to confirm the current per-address timing. Done means one total deadline is shared across all resolved addresses so the endpoint attempt stays within the documented timeout.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
rust
Área
databases
Tipo de issue
Error
Dificultad
3/5
Tiempo estimado
1-2 días
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
68/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.