Say whether an agent's model was configured or reported by its runtime

Abierto
#286 1 comentario 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust

Línea de trabajo

Trace how the app reads agent lists and inspections, then find where each view displays an agent's model. Use the service fixtures at crates/roster/src/profiles/runs/fixtures/agents.json and agent-inspect.json to check model_source values, including unknown ones. Done when the model display distinguishes runtime-reported from configured models in plain words, and the app sends no changed data to the service.

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

Descripción

What is wanted

Where the app shows an agent's model, say whether it is the model the agent was started with or the one its runtime reported.

Why

The Rust Backbone service sends two fields for an agent: model and model_source. Once a runtime has reported its own model, model is the reported one and model_source reads observed; before that it is the configured or default one (runtime_default in the service's fixtures). The model that was asked for is not in that reply once a runtime has reported.

The app reads model and not model_source, so it cannot tell the two apart. The private trial of setup schema 3 (#256, second run) showed the case: the first agent was asked for one model, and the roster carried another name, the one the runtime itself reported.

Acceptance (minimum)

  • The app reads model_source from the agent list and the agent's inspection, and tolerates values it does not know.
  • Where a model is shown, a reported one is told apart from a configured one in plain words, without a new control.
  • No change to what is sent to the service.

Notes

  • The service's own fixtures already carry the field (crates/roster/src/profiles/runs/fixtures/agents.json, agent-inspect.json), so tests can use them as they are.
  • Found by the trial, not by a person's report: it waits for the current queue.
Lenguaje dominante
Rust
Estrellas
2
Forks
0
Merge medio
4 h 30 min
PR fusionados (30 d)
193

Preparar el entorno

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 eandualem/agent-interface

Todos los issues de eandualem/agent-interface

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.