Distinguish monotonic clock failures from expired async deadlines

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

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

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

Línea de trabajo

Begin with std/task/net.wave around line 22 and trace the _remaining() helper through initial deadline creation, later async waits, and I/O. Discuss the result/error contract with @LunaStev before implementation, since the issue explicitly requires design agreement. Done means controlled clock failures retain their native identity and partial I/O counts, while expiration, infinite waits, and normal deadlines remain distinguishable and behaviorally unchanged.

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

Descripción

discussion enhancement help wanted

Motivation

_remaining() returns zero both when the deadline has expired and when _now() reports failure. A verbatim-helper controlled-clock fixture returns remaining=0 for a clock error. Initial deadline creation instead reports invalid arguments; both paths erase the clock failure.

Starting point: std/task/net.wave:22.

Validation

Audited canonical Wave 540728c2eb6cc12f5c69c3fb3fdb96e07ba059a4 (0.0.1-alpha-dev), whose tree matches the local checkout. Validation: Executed verbatim _remaining helper with a controlled failing clock; no OS clock fault claimed. Executed compiler probes use the matching checkout-built compiler and std on Linux amd64 (Rust 1.89.0 / LLVM 21.1.8). Source/header or mocked checks are not native execution on another OS.

Scope

Choose a small result/error contract that preserves clock failures through async waits and I/O, instead of converting them into a timeout or invalid input. This is separate from the numeric timeout errno mapping.

Design discussion required

This issue records a proposal or an unresolved contract; it is not approval to choose new semantics. Please mention @LunaStev to discuss the design before starting implementation.

Completion criteria

  • Controlled initial and later clock failures are distinguishable from actual expiration.
  • Partial I/O counts and the native failure identity are preserved as agreed.
  • Infinite waits and normal deadlines keep their current behavior.
Lenguaje dominante
Rust
Estrellas
56
Forks
21
Merge medio
23 h 20 min
PR fusionados (30 d)
45

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 wavefnd/Wave

Todos los issues de wavefnd/Wave

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.