keith/MeshVault
1
0 Fork 0
Code Issues 44 Pull Requests Actions Packages Projects Releases Wiki Activity

Per-file import failure capture #27

New Issue
Open
opened 2026-10-10 22:21:52 +00:00 by keith · 1 comment
keith commented 2026-10-10 22:21:52 +00:00
Owner
Copy link
Copy source

Context

Implement this MVP work package under M3 - Import & Indexing Engine, following the managed-storage decision in #1.

Acceptance criteria

  • Persist source path, error code and human-readable reason for each unreadable, invalid or failed item.
  • Continue independent files after individual failures; global storage failure may abort with a clear reason.
  • Expose failures per job, retain prior results on retries, redact secrets and test partial-success runs.

Blocked by: #25

## Context Implement this MVP work package under M3 - Import & Indexing Engine, following the managed-storage decision in #1. ## Acceptance criteria - [ ] Persist source path, error code and human-readable reason for each unreadable, invalid or failed item. - [ ] Continue independent files after individual failures; global storage failure may abort with a clear reason. - [ ] Expose failures per job, retain prior results on retries, redact secrets and test partial-success runs. Blocked by: #25
keith added this to the M3 - Import & Indexing Engine milestone 2026-10-10 22:21:52 +00:00
keith added the area:indexertype:featurepriority:medium labels 2026-10-10 22:21:52 +00:00
keith commented 2026-10-12 18:55:37 +00:00
Author
Owner
Copy link
Copy source

Acceptance reconciliation at c1ef2ee: keeping open. Failure persistence exists, but supported retry with attempt history is absent. Raw exception messages are persisted; safe logging alone does not redact stored failure text. This is a source/test review, not a newly executed crash or restore experiment. Fresh Windows suite: 291 tests, 1801 assertions, 22 skips; lint passes. PostgreSQL fixture success does not waive these feature criteria.

Acceptance reconciliation at c1ef2ee: keeping open. Failure persistence exists, but supported retry with attempt history is absent. Raw exception messages are persisted; safe logging alone does not redact stored failure text. This is a source/test review, not a newly executed crash or restore experiment. Fresh Windows suite: 291 tests, 1801 assertions, 22 skips; lint passes. PostgreSQL fixture success does not waive these feature criteria.
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
area:backend
PHP application logic
 area:db
PostgreSQL schema and migrations
 area:frontend
PHP views, Tailwind, browser JS
 area:indexer
Scanning, hashing, import pipeline
 area:infra
Docker, CI, deployment
 priority:high
Blocking or critical path
 priority:low
Nice to have
 priority:medium
Normal priority
 type:bug
Defect
 type:chore
Tooling, scaffolding, maintenance
 type:decision
Architecture decision record
 type:docs
Documentation
 type:feature
New user-facing capability
No labels area:indexer priority:medium type:feature
Milestone
No items
No Milestone M3 - Import & Indexing Engine
Projects
Clear projects
No projects
Assignees
Clear assignees
keith (Keith Solomon)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: keith/MeshVault#27