domverse/photoanalyzer
1
0
Fork 0
Code Issues 5 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

US07-03 — Harden Media and Metadata Edge Cases #40

New Issue
Open
opened 2026-07-13 13:10:52 +02:00 by domverse · 1 comment
domverse commented 2026-07-13 13:10:52 +02:00
Owner
Copy Link

Source specification: delivery_backlog/stories/US07-03-media-hardening.md

US07-03 — Harden Media and Metadata Edge Cases

Epic: E07

As a user, I want unusual or damaged media handled safely so one file cannot corrupt
metadata, exhaust resources, or stop the library workflow.

Acceptance criteria

  • Supported format/orientation/profile combinations have bounded decode behavior.
  • Corrupt, truncated, huge-dimension, unsupported, and malformed-metadata files become
    precise item errors without worker failure.
  • EXIF checkpoints preserve user fields and previous-stage fields, read back owned
    fields, and mark conflicts divergent rather than silently repairing them.
  • Cache regeneration/invalidation and temporary-file cleanup are safe and scoped.

Automated tests

  • Extended golden corpus covers all declared format, orientation, corruption, and EXIF
    cases with memory/time bounds and before/after metadata snapshots.

Dependencies

  • US07-01
Source specification: [delivery_backlog/stories/US07-03-media-hardening.md](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/stories/US07-03-media-hardening.md) # US07-03 — Harden Media and Metadata Edge Cases Epic: [E07](https://git.domverse-berlin.eu/domverse/photoanalyzer/src/branch/main/delivery_backlog/E07-hardening-release.md) As a user, I want unusual or damaged media handled safely so one file cannot corrupt metadata, exhaust resources, or stop the library workflow. ## Acceptance criteria - Supported format/orientation/profile combinations have bounded decode behavior. - Corrupt, truncated, huge-dimension, unsupported, and malformed-metadata files become precise item errors without worker failure. - EXIF checkpoints preserve user fields and previous-stage fields, read back owned fields, and mark conflicts divergent rather than silently repairing them. - Cache regeneration/invalidation and temporary-file cleanup are safe and scoped. ## Automated tests - Extended golden corpus covers all declared format, orientation, corruption, and EXIF cases with memory/time bounds and before/after metadata snapshots. ## Dependencies - US07-01
domverse added this to the E07 — Hardening and Release milestone 2026-07-13 13:10:52 +02:00
domverse added a new dependency 2026-07-13 13:11:32 +02:00
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse added a new dependency 2026-07-13 13:11:34 +02:00
#44 US07-07 — Automate Full Release Acceptance
domverse added this to the Photo Analyzer Delivery project 2026-07-13 13:19:48 +02:00
domverse added the status/backlog label 2026-07-13 13:52:56 +02:00
domverse added status/in-progress and removed status/backlog labels 2026-08-16 23:09:19 +02:00
domverse self-assigned this 2026-08-16 23:09:19 +02:00
domverse commented 2026-08-16 23:09:20 +02:00
Author
Owner
Copy Link

Claimed for implementation on branch us/US07-03-harden-media-and-metadata-edge-cases.

Claimed for implementation on branch `us/US07-03-harden-media-and-metadata-edge-cases`.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/backend
Backend services, jobs, or API
 area/database
Schema, persistence, migration, or queries
 area/filesystem
Filesystem identity, mutation, or storage
 area/frontend
Browser UI and client-side application
 area/integration
External tools or provider integrations
 area/testing
Automated test suites, fixtures, and tooling
 priority/critical
Release-blocking safety or correctness
 priority/high
Important phase outcome
 priority/normal
Normal planned work
 status/backlog
Awaiting dependency eligibility or prioritization
 status/blocked
Cannot proceed without an explicit resolution
 status/done
Merged, tested, and completed
 status/in-progress
Currently being implemented
 status/ready
Eligible to be claimed
 status/review
Submitted in a pull request for review
 type/feature
User-facing or domain capability
 type/hardening
Security, resilience, operations, or release hardening
 type/migration
Donor extraction, migration, or legacy consolidation
 type/test
Automated test infrastructure or acceptance coverage
No Label area/backend area/filesystem area/integration priority/normal status/in-progress type/hardening
Milestone
No items
No Milestone E07 — Hardening and Release
Projects
Clear projects
No project Photo Analyzer Delivery
Assignees
Clear assignees
domverse
No Assignees domverse
1 Participants
Notifications
Due Date
No due date set.
Blocks
#41 US07-04 — Prove Concurrency and Crash Recovery
domverse/photoanalyzer
#44 US07-07 — Automate Full Release Acceptance
domverse/photoanalyzer
Depends on
#38 US07-01 — Complete Donor Migration and Freeze the CLI Archive
domverse/photoanalyzer
Reference: domverse/photoanalyzer#40
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?