Refresh changed/deleted sources with resumable bounded jobs

Aperta
  • Qualcosa non va?
#41 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
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
javascript, node.js
Ambito
backend, databases, security

Direzione di ricerca

Read AGENTS.md and docs/PROJECT_CONTEXT.md, then inspect the cache/index adapters and src/index.js alongside the contracts from #38 and #39. Discuss the design with the maintainer before implementation. Done means resumable bounded jobs handle interruptions, source changes and deletions, revoked enrollment, concurrent updates, account switching and restart, with offline tests verifying no duplicate chunks and safe progress and error output.

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

Descrizione

area:backend area:docs priority:medium status:blocked type:feature

Part of #28 · Target: Durability / v0.6

Goal and scope

Add incremental refresh/status/cancel/resume operations with bounded work, interruption recovery and changed/deleted/denied-source handling. Invalidate outdated derived content without leaking it across accounts. Report checked/stale/failed scope.

Implementation starting points

cache/index adapters, new refresh job state, src/index.js. 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

Depends on #38, #39. Discuss the design before starting implementation; dependent contracts must land first.

Out of scope

No background polling/notifications by default, unbounded full crawl or persisted sessions.

Acceptance criteria and test plan

Tests simulate interrupted jobs, source replacement/deletion, revoked enrollment, stale data, concurrent updates, account switching and restart. Resumption avoids duplicate chunks and progress/errors contain counts and safe codes rather than private content.

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.