Distinguish monotonic clock failures from expired async deadlines

Offen
  • Stimmt etwas nicht?
#1,007 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
32/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
networking

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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.
Vorherrschende Sprache
Rust
Sterne
56
Forks
21
Ø Merge
23 Std. 20 Min.
Gemergte PRs (30 T.)
45

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus wavefnd/Wave

Alle Issues in wavefnd/Wave

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.