riplex 0.6.2__tar.gz → 0.6.3__tar.gz

{riplex-0.6.2 → riplex-0.6.3}/.github/ISSUE_TEMPLATE/bug_report.yml

@@ -13,7 +13,7 @@ body:
     id: version
     attributes:
       label: riplex version
-      placeholder: "e.g. 0.1.1.dev18"
+      placeholder: "e.g. 0.4.1"
     validations:
       required: true
 

riplex-0.6.3/.github/ISSUE_TEMPLATE/crash_report.yml

@@ -0,0 +1,82 @@
+name: Crash Report
+description: Report an unhandled exception / crash in riplex (auto-filed from the GUI's "Report Crash" button)
+title: "[Crash] "
+labels: ["bug", "crash"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for reporting a crash! Most fields below are pre-filled by the
+        GUI. Please review and add anything else that might help reproduce.
+
+  - type: input
+    id: version
+    attributes:
+      label: riplex version
+      placeholder: "e.g. 0.4.1"
+    validations:
+      required: true
+
+  - type: input
+    id: platform
+    attributes:
+      label: Platform
+      placeholder: "e.g. Windows-11-10.0.26100-SP0"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: frontend
+    attributes:
+      label: Frontend
+      options:
+        - CLI
+        - GUI
+    validations:
+      required: true
+
+  - type: input
+    id: exception-type
+    attributes:
+      label: Exception type
+      placeholder: "e.g. FileNotFoundError"
+    validations:
+      required: true
+
+  - type: input
+    id: exception-message
+    attributes:
+      label: Exception message
+      placeholder: "e.g. [WinError 2] The system cannot find the file specified"
+
+  - type: input
+    id: last-screen
+    attributes:
+      label: Last screen / action
+      description: Which screen were you on, or what did you click, when the crash happened?
+      placeholder: "e.g. organize_done — clicked Open Folder"
+
+  - type: textarea
+    id: traceback
+    attributes:
+      label: Traceback
+      description: Full Python traceback (auto-filled by the GUI).
+      render: text
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-were-you-doing
+    attributes:
+      label: What were you doing?
+      description: Brief description of the steps leading up to the crash.
+
+  - type: textarea
+    id: debug-files
+    attributes:
+      label: Debug files
+      description: |
+        Please attach the crash dump file referenced above. It contains the
+        full traceback, app state, and recent logs needed to reproduce the
+        crash. If a `_riplex/` debug folder also exists at your output
+        directory, zip it and drag it here as well.

{riplex-0.6.2 → riplex-0.6.3}/.github/copilot-instructions.md

@@ -28,6 +28,20 @@ For the GUI, also include the gui extra:
 pip install -e ".[dev,gui]"
 ```
 
+### Editable-installing dvdcompare-scraper (optional)
+
+By default `dvdcompare-scraper` is pulled from PyPI as a regular install, so
+local edits to that sibling repo (typically at
+`../dvdcompare-scraper/`) do not take effect until a new version is
+published. To pick up scraper changes immediately without bumping the
+version, editable-install it once:
+
+```
+pip install -e ../dvdcompare-scraper
+```
+
+After this, `riplex-ui` and the CLI will use the local checkout directly.
+
 ### macOS extras (Homebrew Python only)
 
 If you installed Python via Homebrew, two additional one-time steps are needed:
@@ -60,6 +74,30 @@ riplex-ui              # Launch the Flet GUI
 
 Do NOT use `python -m riplex` (that errors — riplex is a library package, not runnable). Do NOT use `python -m riplex_cli.main` when the entry point works.
 
+Because `riplex` is editable-installed (`pip install -e .`), any local edit
+to source files under `src/riplex/`, `src/riplex_cli/`, or `src/riplex_app/`
+is live the next time you launch `riplex-ui` or run a `riplex` CLI command.
+No reinstall step is needed for normal development.
+
+## Upgrading dependencies
+
+The only dependency that needs an explicit upgrade is `dvdcompare-scraper`,
+since it's installed from PyPI (not editable). After a new version is
+published (every push to its `main` branch auto-bumps the patch and
+publishes), bump the pin in `pyproject.toml` and run:
+```
+pip install -e ".[dev,gui]" --upgrade
+```
+
+Close `riplex-ui` first if it's running — the `.exe` shim is locked while
+the process is alive and pip will fail with `WinError 32`.
+
+To verify the upgrade picked up the new version:
+```
+py -m pip show dvdcompare-scraper | Select-String Version
+```
+
+
 ## Dry-run default
 
 All destructive commands (`rip`, `organize`, `orchestrate`) are dry-run by default. There is no `--dry-run` flag. Use `--execute` to actually perform the operation.

{riplex-0.6.2/src/riplex.egg-info → riplex-0.6.3}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: riplex
-Version: 0.6.2
+Version: 0.6.3
 Summary: Automates the tedious manual work around MakeMKV: figuring out what to rip, which MKV files are actually what, and organizing everything into Plex-compatible folder structures.
 License: MIT
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
 License-File: LICENSE
 Requires-Dist: httpx>=0.27
-Requires-Dist: dvdcompare-scraper>=0.1.12
+Requires-Dist: dvdcompare-scraper>=0.1.15
 Requires-Dist: platformdirs>=4.0
 Provides-Extra: dev
 Requires-Dist: pytest>=8.0; extra == "dev"

{riplex-0.6.2 → riplex-0.6.3}/docs/changelog.md

@@ -4,6 +4,18 @@ All notable changes to the riplex documentation are recorded here.
 
 The format is based on [Keep a Changelog](https://keepachangelog.com/).
 
+## 2026-05-13
+
+### Changed
+
+- Bumped `dvdcompare-scraper` pin to `>=0.1.15`, which adds quoted-title disc-header parsing. Boxsets such as *Back to the Future 40th Anniversary Trilogy* that glue six physical discs into a single dvdcompare disc entry are now split correctly into one PlannedDisc per physical disc.
+
+## 2026-05-12
+
+### Added
+
+- Troubleshooting guide: new "GUI: disc not being detected" section covering the redesigned drive-list panel, manual drive selection, the `makemkvcon` status line, and the bundled bug-report flow.
+
 ## 2026-05-09
 
 ### Changed

{riplex-0.6.2 → riplex-0.6.3}/docs/troubleshooting.md

@@ -35,6 +35,25 @@ Common issues and solutions reported by users.
 
 ---
 
+## GUI: disc not being detected
+
+**Symptom:** `riplex-ui` shows "No disc found" or sits on the disc detection screen even though a disc is inserted.
+
+**What the GUI does:**
+
+* On the **Disc Detection** screen, riplex now lists every optical drive your system reports, with a per-drive status badge (`Empty`, `Tray open`, `Disc loaded`, etc.).
+* The list refreshes automatically every few seconds — inserting or ejecting a disc updates the screen without manual refresh. Click the circular ↻ button at the top right to force an immediate rescan.
+* If exactly one drive has a loaded disc, riplex starts reading it automatically. With multiple drives or zero loaded drives, click `Read disc` next to the drive you want to use.
+
+**If your drive is missing entirely:**
+
+1. Confirm MakeMKV sees the drive. Open the MakeMKV GUI or run `makemkvcon -r info list` and look for a `DRV:` line with your device path.
+2. If MakeMKV does not list it, the issue is at the OS/driver level — riplex only displays what MakeMKV reports.
+3. Check the `makemkvcon: …` line at the top of the screen. If it shows `unavailable`, click the bundled "Download MakeMKV" link or follow the [installation guide](getting-started/installation.md).
+4. Use the `Open bug report` button on the error panel — it pre-fills the GitHub issue with the captured MakeMKV diagnostics (executable path, version, last error) and points you at the log directory to attach.
+
+---
+
 ## Invalid config file (TOML parse error)
 
 **Symptom:** Running any riplex command crashes with a `TOMLDecodeError` traceback mentioning your config file.

riplex-0.6.3/issues/debug-artifacts-consolidation.md

@@ -0,0 +1,146 @@
+# Consolidate riplex debug artifacts
+
+## Problem
+
+riplex currently writes 11 distinct JSON/log artifacts across multiple
+locations with overlapping naming. The word "manifest" is overloaded
+(production `_rip_manifest.json` vs. debug `riplex-rip.manifest.json`),
+two debug writers (`save_rip_manifest`, `save_scan_snapshot`) have no
+production readers, and the organize snapshot lives at the title root
+instead of in `_riplex/` like the other debug files. The `_riplex/README.txt`
+template lists files that may not actually be present.
+
+A related bug: failed rips silently produce a `_rip_manifest.json` with
+`"filename": ""` because `run_rip` checks `proc.returncode == 0` to
+determine success, but `makemkvcon` returns 0 even on HashCheck failures.
+Surfaced by a real failure on Matrix Reloaded Disc 1 (corrupt
+`/BDMV/STREAM/00002.m2ts`).
+
+## Affected users
+
+Anyone filing bug reports (confused about which JSON to attach), anyone
+inspecting their rip output (unclear what each file is for), anyone
+re-running organize on a failed rip (manifest claims success).
+
+## Workaround
+
+None — symptom is cosmetic confusion plus the failed-rip status bug,
+which can be diagnosed by reading `_makemkvcon_tNN.log` directly.
+
+## Proposed fix
+
+### Target artifact layout
+
+**Per-disc folder** (production + per-title logs):
+
+- `Disc N/<canonical>_tNN.mkv` — actual rip
+- `Disc N/_rip_manifest.json` — production; gains a per-title `status`
+  field (`"success"` | `"failed"` | `"cancelled"`) plus `error_message`
+  for failures, and top-level `success_count` / `failed_count`
+- `Disc N/_makemkvcon_tNN.log` — stays here (per-title, too noisy for
+  the title-level debug folder)
+
+**Title-root `_riplex/`** (single home for all debug):
+
+- `riplex-rip.snapshot.json` — rip pipeline state (TMDb match,
+  dvdcompare, selected/ripped titles, phase)
+- `riplex-organize.snapshot.json` — **renamed and moved** from
+  `<Title>.snapshot.json` at title root
+- `organized.json` — already lives here, unchanged
+- `riplex.log` — CLI session log, unchanged
+- `README.txt` — rewritten to match what's actually written
+
+**User-data folder** (`~/.../riplex/`) — unchanged:
+
+- `riplex_app.log` — GUI runtime log
+- `crashes/crash-*.txt` — GUI crash dumps
+
+**Removed entirely**:
+
+- `_riplex/riplex-rip.manifest.json` — duplicate of production manifest,
+  no readers
+- `_riplex/riplex-scan.snapshot.json` — aborted parallel mechanism, no
+  production readers (only tests)
+
+### Implementation phases
+
+1. **Manifest status field.** Real success detection in `run_rip` (parse
+   `MSG:5004,...,"N titles saved, M failed"` summary line). Update
+   `build_rip_manifest` to include all attempted titles with `status` +
+   `error_message`. `build_scanned_from_manifests` skips non-success
+   entries. `load_manifest` defaults `status` to `"success"` when
+   missing for back-compat. Independent of other phases. (Partially
+   implemented: `_parse_rip_summary` already added in
+   `src/riplex/disc/makemkv.py`.)
+
+2. **Consolidate organize snapshot.** New path
+   `_riplex/riplex-organize.snapshot.json`. `snapshot.py::load()` falls
+   back to legacy `<Title>.snapshot.json` for old folders (no
+   migration). Updates callers in `organize.py` and
+   `organize_preview.py`. Independent of phase 1.
+
+3. **Remove dead writers.** Delete `snapshot.py::save_rip_manifest()`
+   and `snapshot.py::save_scan_snapshot()` plus their callers. Drop
+   corresponding tests. Depends on phase 2.
+
+4. **Docs + README template.** Rewrite `_README_TEXT` in `snapshot.py`
+   to match reality. New "Output Artifacts" section in
+   `docs/architecture.md` with the full table (production vs debug,
+   location, writer, reader, safe-to-delete). Dated entry in
+   `docs/changelog.md`. Same commit as phases 2-3 so docs match code.
+
+5. **Patch version bump** per repo convention.
+
+### Decisions locked
+
+- Heavy scope: consolidate file locations + rename + remove dead code +
+  docs (not just docs)
+- "manifest" reserved for production data; debug duplicate is deleted,
+  not renamed
+- Both `save_rip_manifest` and `save_scan_snapshot` removed
+- `_makemkvcon_tNN.log` stays in per-disc folder (too noisy/per-title to
+  belong alongside the higher-level pipeline snapshots)
+- Failed rips DO get a `_rip_manifest.json` entry with `status: "failed"`
+- No migration tool for old organize snapshots — `load()` just tries new
+  path first, falls back to legacy
+
+### Verification
+
+1. `pytest` — existing tests pass; new tests for status field +
+   legacy snapshot fallback
+2. Fresh GUI rip → output dirs contain only files in the north-star
+   list above
+3. Cancel a rip mid-way → manifest has `status: "cancelled"` entry
+4. Re-rip Matrix Reloaded Disc 1 (the damaged disc that prompted this)
+   → manifest has `status: "failed"` with `error_message` populated
+5. Run organize against a folder containing legacy
+   `<Title>.snapshot.json` → loads via fallback
+6. Open `_riplex/README.txt` in a finished session → matches files
+   actually present
+7. Visual: title folder structure matches `docs/architecture.md` table
+   exactly
+
+### Out of scope
+
+- User-data log locations (`riplex_app.log`, crash dumps)
+- Migration tool for old `<Title>.snapshot.json` (just fallback-read)
+- v1/v2 snapshot envelope format (already supported by `load`)
+- `_makemkvcon_tNN.log` location/format
+- GUI changes beyond the manifest status fix already started
+
+## Relevant files
+
+- `src/riplex/manifest.py` — `build_rip_manifest`,
+  `build_scanned_from_manifests`, `load_manifest`
+- `src/riplex/snapshot.py` — `save_rip_snapshot`, `save_rip_manifest`
+  (DELETE), `save_scan_snapshot` (DELETE), `save_from_scanned`, `load`,
+  `_README_TEXT`, `get_debug_dir`
+- `src/riplex/disc/makemkv.py` — `run_rip`, `_parse_rip_summary`
+- `src/riplex_cli/commands/rip.py` — remove `save_rip_manifest` call
+- `src/riplex_cli/commands/organize.py` — organize snapshot path
+- `src/riplex_app/screens/organize_preview.py` — organize snapshot path
+- `src/riplex_app/screens/progress.py` — `_write_manifest`
+- `tests/test_snapshot.py`, `tests/test_manifest.py` — fixtures, drop
+  deleted-fn tests, add status-field tests
+- `docs/architecture.md` — new Output Artifacts section
+- `docs/changelog.md` — dated entry