Distinguish monotonic clock failures from expired async deadlines

Aperta
  • Qualcosa non va?
#1,007 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
32/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
networking

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.
Lingua principale
Rust
Stelle
56
Fork
21
Merge medio
23h 20m
PR unite (30g)
45

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/Wave

Tutte le issue di wavefnd/Wave

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.