Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Four [limits] keys are accepted and not read or enforced

Abierto
  • ¿Algo no está bien?
#538 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

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
Bien especificado
Estado de actividad
Activo
Stack tecnológico
rust
Área
backend

Línea de trabajo

Start by tracing LimitsConfig and the named paths: crates/auth/src/policy/document.rs, crates/engine/src/create_table.rs, crates/core/src/validation/mod.rs, and crates/engine/src/describe_limits.rs. Follow the existing policy read/write paths and table creation and update validation to decide how each configured limit is handled. Done means each key either affects enforcement as described or is removed from LimitsConfig; the expected errors are specified in the issue.

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

Descripción

Four [limits] keys are accepted by the configuration loader and documented, and the server does not act on them.

  • max_policy_document_bytes (crates/core/src/limits/mod.rs) has no reader. The policy document size check is PolicyDocument::from_json, which calls from_json_with_size_limit(json, 6_144) with a literal (crates/auth/src/policy/document.rs:157); both callers use from_json. Changing the key changes nothing.
  • max_tables_per_account is read only by the console settings page. CreateTable (crates/engine/src/create_table.rs) does not count the account's tables, so the limit is never enforced.
  • per_table_max_rcu and per_table_max_wcu are read only by DescribeLimits (crates/engine/src/describe_limits.rs), which reports them. Provisioned throughput validation (crates/core/src/validation/mod.rs) checks that each value is at least 1 and has no upper bound, so CreateTable and UpdateTable accept any value.

The configuration reference (#537) now describes each key as it behaves. This issue is the other half: either wire the keys (pass max_policy_document_bytes into from_json_with_size_limit on the write and read paths; count tables in CreateTable; bound provisioned throughput in validation) or remove them from LimitsConfig so an operator cannot set a limit that does nothing. The service rejects a table count above the account quota with LimitExceededException and a provisioned value above the per-table maximum with ValidationException; the messages are measured before any enforcement is written.

Found while checking every configuration key against the code that reads it, for #494.

Lenguaje dominante
Rust
Estrellas
517
Forks
60
Merge medio
2 d 23 h
PR fusionados (30 d)
25

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 ExtendDB/extenddb

Todos los issues de ExtendDB/extenddb

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.