A busy Home told people their hosted model grant was inactive

Abierto
  • ¿Algo no está bien?
#561 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
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
1/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
authentication, backend

Línea de trabajo

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.

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

Descripción

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.

Lenguaje dominante
Rust
Estrellas
6
Forks
2
Merge medio
1 d 3 h
PR fusionados (30 d)
42

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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

Todos los issues de elastos/elastos-runtime

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.