[BUG] record.set reports a rejected value as internal: engine/transport failure

Abierto
  • ¿Algo no está bien?
#454 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend-api-design

Línea de trabajo

Read aimdb-core/src/typed_record.rs around line 1524 to understand the rejected value error, then trace how map_db_err in aimdb-core/src/session/aimx/dispatch.rs maps it and how RpcError is decoded in aimdb-client/src/engine.rs and aimx/codec.rs. The issue calls for a distinct wire error code that preserves the deserialization message while keeping engine and transport failures internal. Done means rejected values produce the specific error and unknown codes still fall back as described; the issue does not name tests to run.

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

Descripción

bug

Describe the bug
When a remote record.set value fails to deserialize into the record's type, the client gets the same error as a broken engine or transport:

AimDB client error: Server error (code internal): engine/transport failure

The write is refused correctly and the session stays up. The problem is the report: a caller, especially an MCP agent, cannot tell that its own value was at fault, so it has no reason to correct it.

The server does build a specific message (typed_record.rs:1524), but it is lost on the way out:

  • map_db_err sends everything except not-found and permission errors to RpcError::Internal.
  • RpcError carries no message, so the client fills in its generic text (engine.rs:593).

To Reproduce

  1. Run an instance with a writable record whose type rejects some JSON, for example a custom deserializer that bounds a list's length.
  2. Call record.set (or MCP set_record) with a value that type rejects.
  3. See the error above.

Observed with a list over its bound (33 and 2000 elements against a limit of 32). A coordinate of 1e40 for an f32 field got the same reply; I did not trace that case separately.

Expected behavior
A distinct error code for a value the record's type rejected, separate from internal, ideally carrying the deserialization message. Real engine and transport failures keep internal.

Environment

  • OS: macOS 13 (Darwin 22.6)
  • Rust Version: rustc 1.98.0
  • AimDB Version: main at d9c7be0

Additional context
A new code changes the AimX wire vocabulary, so existing clients need to handle it. code_err in aimx/codec.rs currently maps unknown codes to Internal, so older clients would fall back to today's behaviour.

Lenguaje dominante
Rust
Estrellas
101
Forks
20
Merge medio
2 h 33 min
PR fusionados (30 d)
90

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 aimdb-dev/aimdb

Todos los issues de aimdb-dev/aimdb

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.