A busy Home told people their hosted model grant was inactive

Aberta
  • Algo errado?
#561 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
1/5
Tempo estimado
Menos de uma hora
Facilidade para iniciantes
1/100
Tipo de issue
Bug
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
authentication, backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
6
Forks
2
Merge médio
1d 3h
PRs com merge (30d)
42

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de elastos/elastos-runtime

Todas as issues de elastos/elastos-runtime

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.