A conversion job could still do something its confirmed dry run did not show,
or refuse what it should have converted:
- An upload landing between the confirmation and the sequence's turn made the
sequence Changed at every retry. Each ConvertSequence now names the photos
the plan converts (Photos, their frame ids); the job takes those from its
re-plan, checks their content against the confirmed digest and leaves photos
that came in since as they are. A photo the plan did not list is never
converted, whatever changed on disk or in the index since the dry run.
- A file another program held during the dry run was planned as Missing and
then converted or not depending on the re-plan. It is now its own reason
(inaccessible, "held open or cannot be opened"); a truncated file reads as
undecodable. At job time a confirmed photo that cannot be opened leaves the
sequence Blocked for the retry; a held photo the job does not convert does
not hide a real change.
- The same sequences could be converted twice (two dialogs or tabs, a lost
answer, no dry run at all). MassConverter.QueueAsync checks the queued,
running and paused conversions and queues under one lock, in the caller's
context (the desktop's enqueue shows a toast on the UI thread); a job's own
re-plan treats sequences of conversions queued before it as busy.
- The per-photo space check reserved a full batch of photos even when fewer
were left, so a job whose preview had the space could stop at every retry.
It now reserves the photo and those after it that may convert at once.
- New sequence now says in the dry run, the panel's totals and confirmation,
and a new desktop confirmation, how many photos each new sequence lacks;
only sequences that are copied use those words.
- On the server, a confirmation takes only the plan kept for the index as it
is now (503 plan_dropped otherwise, never a plan made inside the request),
and busy sequences and free space are as they are at every request. The
panel's Apply asks the dry run again first, with Close still available,
and confirms only the same fingerprint.
- Maintenance keeps another host's conversion staging as long as its journal
and purges both together; the unstaged-copy failure and blocked sequences
are logged in catalog sentences.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit fefd9c34ebfeed1f9e84161610ef286026d38355)
The convert endpoint planned the whole selection inside the HTTP request, again for
every mode, quality keystroke and confirmation, with no limit: behind a proxy an
all-sequence conversion could never get past its dry run or its apply.
- ReorganizePlanCache becomes PlanCache, shared by Reorganize and Convert: one plan
per key made apart from the request, two at once across both kinds, eight kept,
15-minute timeout, 5-minute lifetime, 503 plan_dropped. Keys are typed records
(ReorganizePlanKey, ConvertPlanKey) that also say which exceptions are refusals.
- A conversion plan is keyed by archive, a convert stamp of the index
(SequenceRepository.GetConvertStampAsync: the Reorganize stamp plus, per planned
sequence, the photos' count, sizes, formats, pixel sizes and missing, corrupt,
preview-only and undecodable flags), the sequences and the target with the
quality that counts. Not the mode: the request's mode and options are set on the
kept plan, and the free space is measured again at every request through the
engine. A plan made while the volume was away is not kept (503 archive_offline).
- New sequence holds the converted copies alone: the dry run says the skipped
photos are not copied into it (Archive.Convert.NotCopied.*, Server.Convert.OnPcNew),
the panel's totals, column and confirmation give the count, and so does the
desktop's summary.
- Panel: the preview is asked in Replace's neutral words; a dry run cut off by a
proxy is asked again while the totals show how long it takes, plan_dropped is
retried once; an apply the server let go plans again, a changed one shows
Admin.Convert.PlanChanged, and one with no answer is not resent (its job may be
queued).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit f0b1e379ce7c08b6d3459ab25ca6214c8f366f6c)
Owner review 2, R7 asks for mass conversion after import on the desktop too, with a choice at
every run between Replace and New sequence. The desktop now uses the engine's conversion, the
same plan and job as the web panel.
- Convert... in the Archive manager's mass operations (the set) and the Library's mass bar (the
selection of one archive; server cards are left out, two archives are refused with their own
reason). The dialog has the format (JPEG, TIFF 16-bit, Linear DNG, the archival default), a
JPEG's quality (1-100, 95) and the mode, which starts unchosen at every open: Apply waits for
it. Each choice has a tooltip that says what becomes of the originals.
- The dry run stays in the dialog and follows the choices: each sequence with its photos and
sizes before and after, the photos that stay as they are with why, the sequences left as they
are (busy, offline, unreadable), a summary and the free space line; a volume without the space
blocks Apply. The mode does not change what converts, so choosing it plans nothing again.
- Apply asks to type the number of photos a Replace replaces, then queues the convert job of
exactly the plan shown; New sequence leaves the originals as they are and asks nothing.
- When a Replace job ends, its toast offers Undo: for each sequence it converted, the newest
Replaced trash entry made while it ran goes back (a sequence changed since gets its originals
as a new sequence). Undo runs once and never from the Windows notification.
- The Library and the Archive screen read the sequences again after a conversion; --capture
renders archive-convert from a sample plan.
- Strings in en and it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 275469284f895fc92e2569339809e18bf59d1d6a)
(cherry picked from commit 76ba41f58983275ae4b1478edd403efb11da7c79)