A busy Home told people their hosted model grant was inactive

Offen
  • Stimmt etwas nicht?
#561 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
1/5
Geschätzter Aufwand
Unter einer Stunde
Anfängerfreundlichkeit
1/100
Issue-Typ
Bug
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
rust
Bereich
authentication, backend

Rechercherichtung

The issue names gateway_model_service.rs at lines 43, 958, 983, 1299, and 1504, and says the fix is already on a local branch with reviewed commits. Read the grant checks and the linked branch notes first; the change is described as ready, and the remaining stated work is one full Linux check before the first batch after 2.0.1 stable.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

A person using a shared hosted model could be told "model grant is not active" (and Assistant told them to review service access) when the Home was only busy: the model authority read has a 1 second deadline (gateway_model_service.rs:43, :958), and every read error, including that timeout, became a denial (:1299, and again before dispatch through grant_is_active, :983, :1504).

Found because shared_hosted_offer_denies_fresh_creates_and_recovers_without_losing_old_runs failed twice under the full suite on unrelated branches (lesson 1231): the audit activation and principal-root mutexes were one lock for every Home in the process, so another test Home held them past the deadline.

Fix ready on branch fix/flaky-hosted-offer-grant (local, not pushed), written by a Cursor agent (Grok 4.7), reviewed by Codex (GPT): FAIL on round 1, PASS on c4972ed0b.

  • 4454b2c42: the audit and principal-root locks are per Home data directory (writers still serialize on the process-wide mutation lock).
  • c4972ed0b: a timeout is its own result, authority_timeout, at both checks; dispatch is refused and any reservation released; carried through Carrier's allowlist and the consumers; Assistant says "The Home could not check model access in time. Try again."
  • Writer checks: clippy, cargo test -p elastos-server lib 3321, bins 218, integration 1, behaviour suite 2202, source gate, product-ui-source; the original test passed 50 times in a row.

Goes into the first batch after 2.0.1 stable, with one full Linux check.

Vorherrschende Sprache
Rust
Sterne
6
Forks
2
Ø Merge
1 T. 3 Std.
Gemergte PRs (30 T.)
42

Entwicklungsumgebung

Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.

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 elastos/elastos-runtime

Alle Issues in elastos/elastos-runtime

Ähnliche Issues

Weitere Issues zu Rust

Neue Issues direkt in Ihr Postfach

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