A busy Home told people their hosted model grant was inactive

Ouverte
  • Quelque chose ne va pas ?
#561 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
1/5
Temps estimé
Moins d'une heure
Accessibilité débutants
1/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
rust
Domaine
authentication, backend

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

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.

Langage dominant
Rust
Étoiles
6
Forks
2
Merge moyen
1 j 3 h
PR mergées (30 j)
42

Préparer son environnement

Ce projet ne fournit ni conteneur de développement, ni Dockerfile, ni guide de contribution : l'installation est à votre charge. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de elastos/elastos-runtime

Toutes les issues de elastos/elastos-runtime

Issues similaires

Plus d'issues Rust

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.