Audit request, pagination, response and worker resource limits

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

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js, playwright
Ambito
backend, security, testing

Direzione di ricerca

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then trace request handling in src/moodle.js, the readers, worker and job adapters; inspect the protocol tests and existing authorization, safe-error and synthetic-fixture patterns. Start by inventorying request, time, byte, output and cleanup bounds, then add mocked adversarial coverage for the listed failure cases. Done means confirmed gaps are closed, compatibility and buffering limits are documented, and the specified offline checks are reported.

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

Descrizione

area:backend area:docs help wanted priority:medium type:feature

Part of #28 · Target: Reliability / v1

Goal and scope

Inventory all public-tool request/time/byte/output bounds and cleanup behavior. Close confirmed gaps, ensure serialized session operations recover safely, and distinguish network/session/unsupported failures without credential retries. Include upcoming adapters/jobs in the audit checklist.

Implementation starting points

src/moodle.js, readers, worker, job adapters, protocol tests. Follow AGENTS.md and docs/PROJECT_CONTEXT.md; reuse existing authorization, safe-error and synthetic-fixture patterns. New runtime dependencies need a documented reason.

Dependencies and readiness

Ready to discuss/start independently against current master.

Out of scope

No stress testing faculty production services, endless automatic login retries or unsupported memory-sandbox claims.

Acceptance criteria and test plan

Mocked adversarial tests cover pagination loops, redirects, oversized bodies, worker failures, cancellation and resource disposal. MCP stdout stays valid; diagnostics remain safe. Document buffering/native-memory limits and compatibility impact of each concrete fix.

Run the relevant offline tests, npm run check and git diff --check; runtime changes also require npm test and npm audit. Report checks not run. No faculty credentials or private course material are required for a contribution.

Contributing

Comment here before starting so the maintainer can coordinate the approach and avoid duplicate work. Fork the repository, branch from master, and open a focused PR referencing this issue. No assignee or delivery deadline is set; required checks and review apply.

Lingua principale
JavaScript
Stelle
0
Fork
0
Merge medio
1h 20m
PR unite (30g)
14

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 mahmutmft/courses-mcp

Tutte le issue di mahmutmft/courses-mcp

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.