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

Delete with ExpectedVersion: seal is per-process, storage delete is not compare-and-delete, and an acknowledged cross-hub write returns a stale version

Aperta
  • Qualcosa non va?
#6,856 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
databases, distributed-systems, documentation

Direzione di ricerca

Start with Doc/DataMesh/CRUD.md, which currently points to #6673 for these gaps, and with the cross-hub path GetMeshNodeStream(path).Update(...), where the returned version can differ from the owner's committed version. The seal and storage-delete gaps need a design decision, such as a cross-process seal or a DELETE ... WHERE version = $expected, and no cross-process race has been reproduced yet. Done means the acknowledged write returns the owner's version or the doc names the read to use, and the doc links to this issue.

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

Descrizione

bug sev:M

Split out of #6673, whose own defect is verified fixed on memex.meshweaver.cloud (commit 22eb9e448915, fix #6676): a delete naming a stale ExpectedVersion is refused with Conflict (15 of 15), the current version deletes (5 of 5). Doc/DataMesh/CRUD.md still points at #6673 for three remaining gaps:

  1. The delete seal is held only in the deleting process — another process's writer is not stopped by it.
  2. The final storage delete is not a compare-and-delete — the version check happens at the owner, then the row is removed unconditionally.
  3. The version returned by a cross-hub GetMeshNodeStream(path).Update(...) is not the owner's committed version — observed: the returned node carried v1 while the owner held v2 — so the doc's advice "use the version from an acknowledged write as ExpectedVersion" yields a false Conflict (no data lost, but the advice is wrong).

Not established: whether (1)/(2) are reachable in production today (no cross-process race was run); (3) was measured once via the MCP path.

Expected: a cross-process seal or a storage-level conditional delete (DELETE … WHERE version = $expected); the acknowledged-write path returns the owner's committed version, or the doc names the read to use. Update Doc/DataMesh/CRUD.md to point here instead of #6673.

Lingua principale
C#
Stelle
12
Fork
5
Merge medio
5h 44m
PR unite (30g)
968

Preparare l'ambiente

  • Nessun Dockerfile né file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 Systemorph/MeshWeaver

Tutte le issue di Systemorph/MeshWeaver

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.