From 71e890c8f1d50f1628d42ac523c8ea4e44a0b692 Mon Sep 17 00:00:00 2001 From: Claudio Date: Mon, 11 May 2026 00:51:05 +0200 Subject: [PATCH] docs(mule-image): duplicates path strip now shows grandparent/parent Co-Authored-By: Claude Opus 4.7 (1M context) --- containers/120-mule-images.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/containers/120-mule-images.md b/containers/120-mule-images.md index 00053b9..82ef28a 100644 --- a/containers/120-mule-images.md +++ b/containers/120-mule-images.md @@ -82,7 +82,7 @@ For pushes from inside the LXC, gitea creds at `/etc/mule-deploy/git-credentials ### 2026-05-11 — Duplicates view shows parent folder + full-path tooltip -`GET /api/v1/library/duplicates/groups` now includes `filepath` in each member payload. `DuplicatesView` renders a dark bottom-strip on every thumbnail showing the parent folder name (via a `duplicatePathLabel` helper that takes the second-to-last path segment), with the full filepath surfaced through the native `title` tooltip on hover. The dimensions chip moves from bottom-left to top-left so the path strip can run edge-to-edge. `memberToPhoto` finally stops faking `filepath = filename` — the synthetic Photo it hands to `PhotoThumbnail` now carries the real path. +`GET /api/v1/library/duplicates/groups` now includes `filepath` in each member payload. `DuplicatesView` renders a dark bottom-strip on every thumbnail showing the last two folder segments — `…//` (e.g. `…/files/Phone Photos starting 01-26`) via a `duplicatePathLabel` helper. Going up two levels avoids the failure mode where two copies sit under matching parent names (e.g. duplicate `2023/` subfolders under different archives) and the label would collapse. Full filepath surfaces through the native `title` tooltip on hover. Dimensions chip moves from bottom-left to top-left so the path strip can run edge-to-edge. `memberToPhoto` finally stops faking `filepath = filename` — the synthetic Photo it hands to `PhotoThumbnail` now carries the real path. **Infra side-effect during the deploy:** two consecutive `--force-recreate` cycles (deploy.sh and a manual `down/up`) raced and left **orphan duplicate worker containers** (`_mulita-worker-light` + the named `mulita-worker-light`, same for vision) both pulling from the same Redis queue. Worker concurrency was effectively doubled, host load climbed past 120, and `pct exec` into LXC 120 hung for several minutes. Recovery: `docker rm -f` on both orphan IDs. The deploy-gotcha entry below covers the pattern; the new contribution from this session is "look for renamed `_` containers and remove them if you ever see load spike + pct hang after a deploy".