Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Relay rejects host names, so a changing iMotions IP can't be entered as a name

Abierto
  • ¿Algo no está bien?
#240 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

@PRINCEKK122 ya está trabajando en esto.

Desde el 18/10/2026.

  • #242 de @PRINCEKK122 — abierto

Evaluación

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

Línea de trabajo

Start with State::validate_tcp_addr in relay/src/state.rs and check how its result is used when connecting; the issue proposes resolving host:port with ToSocketAddrs. Confirm the client's network need first, since the issue says it is unverified and asks for triage. Done means host names and IPs are accepted, while unresolved names and missing or out-of-range ports produce clear errors.

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

Descripción

area:relay enhancement needs-triage rust

Is your feature request related to a problem? Please describe.
State::validate_tcp_addr (relay/src/state.rs) parses the address as a SocketAddr, so only a literal IP and port are accepted. localhost:9999 and a machine name such as IMOTIONS-PC:<port> are rejected. The README documents this ("localhost:9999 is rejected"), but it may be a problem in the client's lab. Her simulator and iMotions run on different machines (the plugin runs on the simulator machine, iMotions on its own computer), so the relay needs the iMotions computer's network address. If that address comes from DHCP it can change between sessions, and the saved-address dropdown would then hold a stale entry.

Describe the solution you'd like
Accept host:port where host is a name or an IP, resolving it at connect time (ToSocketAddrs), and keep a clear error for a name that does not resolve or a port that is missing or out of range.

Describe alternatives you've considered
Keep literal IPs only and ask the lab to give the iMotions machine a fixed IP. That costs nothing in code but needs the lab's IT. It is worth asking the client before building this.

Additional context
Not confirmed as a real need: we don't know how the lab's network is set up, so this is needs-triage until the client answers whether the iMotions machine has a fixed IP. Related: #195 (which port iMotions listens on) and #139 (saved addresses, closed).

Lenguaje dominante
Rust
Estrellas
4
Forks
9
Merge medio
5 d 13 h
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de oss-slu/PilotDataSynchronization

Todos los issues de oss-slu/PilotDataSynchronization

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.