Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#538 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 4 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Rust
Stelle
517
Fork
60
Merge medio
4g 22h
PR unite (30g)
40

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ExtendDB/extenddb

Tutte le issue di ExtendDB/extenddb

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.