Integrating owner review 2 phase 4a (R7) onto the reviewed phase 3 code.
- RenamePlanner: a sequence already at its expanded folder, or at the " (n)" of it that
filing or an earlier Reorganize gave it, keeps that folder (in the template's case, unless
another sequence holds that exact name). The planner seeded its claimed folders with the
sequence's own, so "2026-09-28 (2)" was planned to "(3)" and back to "(2)" by the next
run; a second Reorganize with the same templates now plans nothing.
- MassRenamer: each step settles what a crash or a busy trash entry left in its sequences
(SequenceWriter.ReadLocked) and waits, as a sequence deletion does, while a restore from
the trash is not settled (FrameTrash.EnsureSettled), before its folder or any file name
changes: that restore's journal names files by the names they had. Trash records keep
restoring after a Reorganize: into the sequence where it is now, under the record's own
name made free (_2) with its companion following.
- Jobs.Kind.Move and Admin.Job.Kind.Move now mean "Reorganize": their old "Move archive"
translations are removed from the 36 other cultures so they are translated again.
- Tests: a second run plans nothing (planner and archive), companions found alike by the
trash and Reorganize whatever their case, a photo deleted before a Reorganize comes back
beside the new names, a Reorganize waits for a busy restore and settles it first.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R7 asks to rename and move sequences after import on the desktop too.
The desktop now uses the engine's Reorganize, the same plan and job as the web panel.
- One Reorganize… dialog replaces Rename… and Move… in the Archive manager and Move… in
the Library. It has three templates: folders, file names and titles. Each one has a
switch and is checked as it is typed. Folders and file names start on, filled from the
archive's settings; titles start off as {title}. Renaming only titles is the Titles
switch alone.
- The dry run stays in the dialog and follows the typing. Each sequence shows its folder,
title and first file names before and after. Sequences carried along with a folder are
marked, and photos that keep their names are listed with the reason. A summary counts
the sequences that change, the files renamed and the names kept.
- Apply no longer changes the archive from the dialog. It queues the engine's move job
with exactly the plan shown (its fingerprint), so the work can be paused, resumed after
a restart and followed in Jobs. The job refuses the plan if the archive changed after
the dry run.
- The Library's Reorganize… works on the selected sequences of one archive. The Archive
screen reads the archive again when a move job ends.
- After Settings › Archive saves a new folder or file template to an archive that holds
sequences, a toast offers Reorganize… for every sequence. Its templates are the ones
changed since; a second change made while the toast is up adds to that toast instead of
opening another.
- Strings in en and it. The keys of the old Rename and Move were removed and pruned from
every translation, so the 36 other languages show the new keys as untranslated instead
of keeping "Move".
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 7bbf451f737a71b768dcd70a77b998daaef851f3)
Owner review 2, R7 asks to rename and move sequences after import, on the web panel too.
The Library's mass bar gets Reorganize… for the selection (every sequence after Select all
without a filter, else at most a thousand ids), and saving a changed folder or file template
on the Archive page offers it for all sequences in the save toast.
The dialog (reorganize.js) has a switch and a field for the folder, file and title templates,
prefilled from the archive settings; each change asks POST /archive/reorganize for a dry run,
one request at a time, and the table shows every step before and after (title, folder, renamed
files with samples, photos that keep their names and why). Apply confirms with the counts of
sequences, folders and photos, sends the shown plan's fingerprint back, and the toast links to
the queued job; a plan_changed refusal plans again. Server refusals land on the field they name.
Toasts can carry an action; the audit entry archive_reorganized reads as a sentence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 13939dff9a1e8a23ce7802ac38f2ded7fdbc2a74)
Owner review 2, R7 asks for renaming and moving after import, on the web panel and the
desktop. This is the engine and the server API both UIs build on.
- FrameNaming (Core/Naming) is the one naming context and unique-name rule of a frame:
imports, uploads and Reorganize now produce identical names (behaviour of the ingest and
the import planner unchanged).
- RenamePlanner takes a file template: each step counts its renamed frames, shows the first
three and the frames version they were planned at, and lists what keeps its name (photos
in place outside originals/, never hashed, missing, unreadable sidecar). Names are given
in index order with _2, _3 as filing does; XMP companions follow their photo.
- MassRenamer renames a step's files under the same leases after its folder moved, checks
the frames version, journals .chronos/rename-files.json and moves files in two phases
through temporary names so chains and swaps never meet; then sidecar, index
(FrameRepository.RenameFilesAsync, both dialects) and journal. A failure puts every file
back; a crash is completed by the next writer or the plan's resume, the index following.
Plans a paused or cancelled job holds are left to that job.
- JobKind.Move gets MoveJobHandler: it plans again and applies only the confirmed plan
(fingerprint and frames versions), with progress and checkpoints per sequence.
- POST /api/v1/archive/reorganize: dry run with the plan and its fingerprint, otherwise a
202 move job; validated templates, audited, sequenceChanged reorganized events.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit aae1c3eb18ea932b4a6251c5e2a282b9295a5785)
The upload dialog's completion helper called `api`, which only exists inside
openUpload, so every web upload failed with a ReferenceError at its last step.
complete() now takes the dialog's api. A new test lexes every admin module and
fails when a top-level function uses api without taking it; it flags the old
upload.js.
During a run Esc is now stopped on the document in the capture phase. The old
listener sat on the dialog, so with the focus on the body (Start disables
itself, a click on the dialog's text) a second Esc closed the dialog and threw
the uploads away. The listener is added when a run starts and removed when it
ends or the dialog closes.
A sequence page refreshes after any ended job, because jobState names no
sequence. That refresh now redraws the header only when the sequence changed,
and the renders only when their list did. Stars, tags and renders are redrawn
through redraw(), so the keyboard focus stays put. restoreFocus finds an
unnamed control by its place, not as the first unnamed one. Failed thumbnails
are retried with a doubling wait and at most 8 tries, counted again once the
sequence changes.
The trash page reads the emptying it follows from /api/v1/jobs/{id} on every
load and after the event socket reconnects (api.events now emits
"reconnected"), so Empty no longer stays disabled when the job's end was lost.
A Restore in flight stays disabled across redraws.
The Library list counts cancelled jobs as ended (shared JOB_ENDED). Comments
are corrected in shared.js and library.js.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 641b9cd96b95d523990d1414c2bdead4138c5f4d)
Second fix round of owner review 2, phase 3 (engine, server, desktop).
- A photo never hashed whose original is missing can be deleted again: it goes
into its trash record without a file and without a tombstone (nothing is left
to name), stays listed until Empty erases it, and a restore keeps it with the
reason "no file". FrameDeleteBlock.Unhashable now blocks only a present
original that cannot be read; the API answers it as 409 photo_unreadable
naming the photo, and every block has its own code and message.
- Deleting a whole sequence first settles an interrupted photo deletion,
restore or ingest of it (ReadLocked under its lease), so no journal or half
entry travels into the sequence's trash entry; it refuses while a restore
into it waits for its busy entry.
- FrameTrash.Settle takes the photo entry's lease and leaves the journal for
later while the entry is busy (an emptying), so it never races EraseAsync;
meanwhile no other restore writes its journal over it and scans do not adopt
its files.
- The hashes computed for frames that stay (to find a twin of a deleted photo)
go into the sidecar and index, and only a frame whose first and last 64 KiB
match a deleted photo's is read whole.
- A restore into a new sequence rewrites its record after each photo filed, so
a crash or a database failure never leaves filed photos listed.
- An upload completion no longer has a window before the commit: the ingest
checks the sidecar's tombstones under the sequence lease a deletion takes
(IngestRequest.RefuseRemoved), unless the upload asked to bring it back.
- A restore reports each kept photo with its reason (no longer matches its
record, could not be moved back, already in the sequence, had no file); the
desktop line and the API message say so in en and it, and the tooltip holds
the whole sentence. The desktop tells TrashMismatchException by its type.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 1858f1f450a35fb8383ede8d80ce5f8de9b7ceac)
The desktop trash dialog sent the "N files stayed in the trash" sentence
through ShowError. ArchiveFailures.Cause has no arm for it, so after a
partial restore the red line and Narrator said "A file of the archive could
not be read or written." The sentence itself appeared only in the tooltip.
The same thing happened to an entry none of whose files matches its record.
- ArchiveDialogViewModel.ShowMessage shows a sentence that is already
localized. The trash dialog uses it for kept files, and its tooltip names
the files kept (six of them, then "+ N more").
- ArchiveFailures.Cause passes FrameTrash's Archive.Error.TrashMismatch
sentence through. It matches the sentence's text because the engine throws
a plain InvalidDataException. Any other InvalidDataException, such as a
sidecar that belongs to another sequence, still reads as a file error.
- Archive.Trash.List, Tooltips.Archive.Trash and Tooltips.Archive.TrashRestore
changed meaning in English: they now cover photo entries as well as
sequences. They are removed from the 36 cultures other than en and it, so
those cultures fall back to English and `i18n check` lists the keys as
untranslated instead of showing the old sequence-only wording.
- The XAML comments describe what the trash dialog and its error line show
now.
Tests: the dialog restores a photo entry and a sequence entry and checks
which rows are left. A photo entry with one tampered file shows the
KeptFiles sentence and keeps its row. An entry with every file tampered
shows the TrashMismatch sentence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 2524a11445c87d37625b01095ef7c2a84a2ee422)
Review fixes for owner review 2, phase 3 (R6 Library on the web panel):
- Trash: the worker can end an emptying before the browser has read the
POST's 202, so its jobState arrived while the page did not know the job
yet; Empty then stayed disabled ("being emptied") and no result showed.
The page now keeps the last state of the jobs that ended and looks its
job up there before following it. Any ended job also reloads the list
(an emptying from another tab or the desktop sends no sequenceChanged),
and a Restore answered 404 shows the trash as it is now.
- Sequence: thumbnail, proxy, verify and analysis jobs send no
sequenceChanged, so tiles and the cover stayed placeholders and the
status chips stale. An ended job now schedules one refresh (not pushed
back by the next): the sequence is read again and failed images are
asked for again under a retry address (shared retryImages).
- Library list: Esc, Ctrl+A or unticking every card left the "Select all"
snapshot in place, hiding Select all and stopping the live refresh from
pruning the selection. It is dropped once no selected sequence lies
beyond the loaded rows; Clear filters clears the selection too.
- The sequences' delete dialog lists at most 500 names (blocked ones
first, with their reasons), like the photos' dialog (shared LISTED).
- Admin.Trash.RestoreSequence.Tip promised a SHA-256 check that a sequence
restore never makes (it moves the folder back); it now says so and names
Verify (en, it; no other culture had the key).
- The upload test's name and comments say what it checks: upload.js is
only imported dynamically, not loaded on click.
Tests pin each change in SystemEndpointTests; the pages were also driven
in a browser against a fake API, where the pre-fix modules fail and the
fixed ones pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 78f66082fd85543d619375574c82cc63a233b7a8)
- frames/delete carries its own request body limit (about 4.8 MB), so the
documented 100,000 ids fit; the server's 1 MiB stopped at about 26,900.
- Restore tells a damaged or foreign sidecar of the target sequence
(409 sidecar_mismatch) from an entry whose files no longer match its
record (422 trash_mismatch, now a TrashMismatchException); frames/delete
answers sidecar_mismatch instead of 500, and 404 when the sequence left
the index between plan and delete, also on the re-plan.
- With the archive offline, the trash list and the empty plan answer
503 archive_offline instead of an empty trash; a read-only archive still
lists and plans but cannot be emptied.
- The empty request is audited as trash_empty_requested: the job checks
the plan again and may erase nothing, so the entry no longer claims an
erase that has not happened.
- API tests for these paths, a named subset emptied, sequence-entry
restore and sequence_in_library, photos restored into a new sequence,
viewer 403 on bulk routes and admin deletes of another user's photos.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit fa35831d55c44746f7f76e0cff262ed6aecf8e72)
Sync:
- A server frame that has not been hashed is known by content only once it is
downloaded: one this PC deleted (or holds as its replacement) is now deleted
from staging instead of filed again, which also dropped its tombstone.
- An unhashed local original that turns out to be a photo the server deleted
is not uploaded, and the archive verify then writes the hashes into the
index, so the row settles instead of offering Upload for good.
- A tombstone leaves a photo out of the comparison only when its side no longer
holds that content, so a tombstone left beside a held copy does not keep the
other side's copy missing forever.
Uploads:
- StartUploadRequest.Restore (optional, never sent by sync or older clients)
lets an explicit user upload file a photo deleted from the sequence again,
also after the trash was emptied; the completion repeats it with
?restore=true and the ingest drops the tombstone.
- The completion checks the tombstone again: a photo deleted while its bytes
were on the way is not filed (409 photo_removed, upload cancelled); the
protocol client reports that as not sent.
- A tombstone of content a frame of the target still holds refuses no repair.
- Hidden dot names (AppleDouble "._" files) are refused, as the archive
scanner leaves them out.
Web upload dialog:
- Upload again on rows marked Deleted before; the tooltip no longer promises
a trash restore that may be impossible.
- Sends a capture time: the Exif DateTimeOriginal of a JPEG or TIFF-based file
(minimal in-house reader, capture-time.js), else the file's time, so photos
without Exif keep their order.
- Esc is stopped at keydown during a run (Chromium allows one prevented cancel
per activation); hidden dot files are left out; a completion refused while
another one files the upload waits for it; the same photo picked under two
names waits for its first copy.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit d051bcfc351f5a08500ca864a6508576a95492a4)
The review of owner review 2 phase 3 found that the photo trash could destroy or
strand originals outside the Empty job and let deleted photos come back.
- A restore into a new sequence stages each original inside its own entry
(<entry>/.restoring), never in a staging folder other restores share or
maintenance sweeps; any failure moves it back, the commit runs to its end once
the file has left, a cancel stops between photos with the record kept true,
and the next restore of the entry puts back what a crash left staged. Nothing
erases a staging folder any more.
- A restore into an existing sequence writes .chronos/restore.pending.json before
its first move; SequenceWriter.ReadLocked settles it (files back into the entry
before the sidecar was written, record rewritten after), cancellation is
checked once before the journal, and a companion that cannot follow puts its
photo back whole. Only an intact frame keeps a trashed copy out.
- A deletion's record keeps a .pending name until its sidecar is written, so the
trash neither lists, restores nor empties half an entry; a failed sidecar
write undoes the moves, and scans settle any of the three journals.
- Photos never hashed are hashed as they go and get their tombstone; a photo
with neither hash nor original blocks the plan (FrameDeleteBlock.Unhashable).
Sidecars rebuilt from the photos, and sequences restored without one, keep
their tombstones; the index drops a tombstone whose content a frame holds.
- Emptying re-reads and re-measures each entry under its lease before erasing.
- Once the sidecar is written a deletion or restore stands when the index cannot
follow (logged; the next scan resyncs it).
- XMP companions are listed once per directory, case-insensitively; a restore
into a new sequence picks a name its companions can follow, and one that still
cannot is kept in the record as a leftover.
- thumbs.pack is re-keyed with the frames on delete and restore, so the queued
pass reuses the thumbnails; the server checks the fingerprint of thumbnails of
frames never hashed too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 0bb631dd83d082e2569b98d127d827adc2e7f899)
The phase 3 packages land together, so the panel's pieces must stay in step:
- Admin files are served with Cache-Control: no-cache and their content
ETag (If-None-Match lists, W/ tags and * honoured). With max-age=3600 a
browser that loaded the panel before an upgrade could run new modules
next to cached old ones for up to an hour; now it revalidates each file
and only what the upgrade changed is sent again.
- The Library's Upload and a sequence's Add photos open upload.js, which
now ships with the panel: the test requires the module (no 404), the
dynamic import and the openUpload({ api, sequence, onDone }) calls.
- Bulk jobs over more than 1000 sequences queue one job per 1000; the
toast now says how many were queued, also when a later chunk failed.
- The live refresh re-reads every loaded row, a thousand per request,
instead of dropping rows beyond the first 1000 back to Load more.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R3: the panel can add photos to an existing or a new
sequence without the desktop app. upload.js is a dialog the library pages
open (openUpload({ api, sequence, onDone })): file picker or drag and drop
(folders are counted and left out: whole-folder import stays on the
desktop), per-photo state, a total bar, Cancel that deletes the started
uploads, and a leave-page guard while sending. Each photo is hashed in a
same-origin module worker with an in-house incremental SHA-256 (8 MiB
reads; crypto.subtle cannot hash in pieces), which runs the FIPS 180-4
known answers and a crypto.subtle cross-check before its first hash and
refuses to hash on any mismatch; the server verifies the hash again.
Chunks go through api.putBytes with the session's CSRF header, two files
and two chunks at a time, retrying no answer, 429 and 503; quota, space
and permission refusals stop the run with the server's message, and a
photo deleted from the sequence shows as deleted before.
server/info now lists the photo extensions the archive files, so the
dialog offers and sends only those. The CSP already allows the worker
(worker-src falls back to script-src 'self'); tests pin that, the module
walk follows the worker, and a browser-shaped upload runs end to end
through the cookie session.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c64c60ab8bb41c102182e284177ac04a56bf1058)
The web panel now manages the library without editing it: the owner can
browse and view sequences and photos, delete sequences and photos into the
archive's trash, restore or empty the trash and run mass operations, as
R6 asks, on top of the engine endpoints of the previous commit.
- Library page right after the Dashboard: search, Year/Camera/Status/Tag
filters fed by a new GET /api/v1/sequences/facets, sort, cards or list
(remembered per browser), lazy cover thumbnails, Load more by cursor,
multi-select with Shift ranges and "Select all N" of the filter, and a
sticky bar for the selection: Analyse, Proxies, Thumbnails, Verify,
Tags (add/remove), Export CSV (client-side) and Delete (dry run, list
of what moves to the trash, then the move). Filters live in the address,
so Back from a sequence finds them again.
- Sequence view (#/library?id=): inline title, tags, rating and notes,
facts, photos in pages of 500 with content-visibility, a photo viewer
(proxy, arrows, Esc, Exif facts), Set cover, Download original, Delete
photos (typing the count above 20 photos), Delete sequence, renders to
download. No video editing controls.
- Trash view (#/library?view=trash, also linked from Archive): entries,
Restore, and Empty (dry run, list, the localised word typed, the plan's
fingerprint sent back, the job followed to its end).
- Live updates from sequenceChanged and jobState; keyboard grid (one tab
stop, arrows, Space, Shift+Space, Enter, Ctrl+A, Esc); RTL, dark theme.
- GET /sequences takes rendered=true|false for the Status filter.
- ui.js: confirmDialog's typed confirmation by name, word or count, with a
list of what the action concerns; formDialog. api.js: putBytes for the
web upload, which the Library imports on demand (upload.js, optional).
- New web icons from icons.py (Image for the Library, trash, grid/list,
arrows, stars, cover); directional glyphs mirror in right-to-left pages.
- Strings in en and it; tests for the facets (both dialects), the rendered
filter, the menu, the modules and the on-demand upload import.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 029cf334f66cb6fa1265b96a6f8faff2964c11ea)
Owner review 2, R6: the web panel manages the library without editing it, so
the engine and the server must delete single photos safely, keep them out of
sync afterwards, and let an administrator restore or finally erase the trash.
- Migration 0008: frame_removals (tombstones by sequence and SHA-256, reason,
replacement); the sidecar gains "removed" (omitted when empty) and frames a
reserved "source"; the indexer writes the tombstones on every sync, so a
rebuild keeps them, and drops a hero frame that is gone.
- FrameTrash: dry run (busy, frames changed, offline, would empty), delete under
the sequence lease with a write-ahead journal that the next writer undoes
after a crash, files to trash/photos/<seq>-<time>/originals with a record,
sidecar without the frames plus tombstones, index sync clearing analyses,
thumbnails and proxies, proxies renamed to follow their frames, follow-up
jobs. Restore re-hashes every file, keeps mismatches in the trash, puts the
same frame records back and drops their tombstones, or files the photos into
a new sequence through the ingest when theirs is gone.
- Project positions on vanished photos are translated by photo and wait as
pending frames, so they come back with a restore.
- Trash entries have a kind (sequence, photos, replaced); emptying is a dry run
with a fingerprint and a new EmptyTrash job (18) that erases exactly the
planned entries, refuses a stale plan and erases replaced originals only
while their replacements still hash right.
- Sync honours tombstones: nothing one side deleted is offered back, local
files are never deleted, replaced photos count as their replacement; the
server answers an upload of a tombstoned SHA-256 as already there.
- Server: sequence thumbnail, photo delete, bulk delete/retag/jobs, trash
list/restore/empty endpoints with their error messages; a verify of
sequences now targets their archive (POST /jobs failed before).
- Desktop trash dialog lists photo entries and empties the trash after a
typed confirmation through the same job.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 35bb56690a1d69eae57153d036e1409201cd73f7)
The audit retention in force ignored the audit clean-up's steps: with the
audit step unticked nothing was deleted, yet Settings › Logs still showed the
age limit. It is now 0 without that step, and setting a limit (Settings › Logs
or CHRONOS_AUDIT_RETENTION_DAYS at start) ticks the step again, so a saved or
fixed retention always takes effect. While the variable fixes a limit above 0,
an edit that drops the step is 409 setting_locked like turning the schedule off.
The admin panel's Scheduled tab disables what the variable fixes (the row's
switch, the form's Enabled and audit step, the age limit) with the locked
tooltip, and points a setting_locked refusal at the field actually refused.
The Copies kept tooltips now say the backups folder keeps as many copies as
the backup schedule that keeps the most; the LastDone and Newest comments
state the real first-copy rule; Keep audit is documented last-writer-wins.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, phase 2 (R10) review findings on the desktop:
- Showing the Scheduled tab (and coming back to Jobs on it) reads the
actions' availability again, as does a Run now answered unavailable;
rows and an open editor follow, so turning proxies on no longer needs a
restart.
- A delete the index refuses keeps the row: the failed call no longer
reads as Deleted (the enum's default), so a live schedule never leaves
the page.
- SchedulerReady completes false when the index (or the engine) does not
open, so the tab shows that the schedules do not run instead of an
empty panel.
- A read of a schedule's last job that started before a live change or a
later read is ignored, so a finished job no longer shows as running.
- The editor's Action, Unit and Priority dropdowns follow a language
change, keeping what was chosen.
- Weekly days in the table read from the UI language's first day, as the
editor's toggles do.
- Backup tooltips no longer promise daily copies with three kept (their
translations are dropped for retranslation); two tooltips now name the
real Settings rows (Proxy size; Spazio su disco › Limite della cache).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c137e2c74cddef299b2e4179ef0417fa4977953c)
- SchedulerHost reads archive.json every 10 minutes on its own timer. The archive-scan
runs that used to do it are skipped while a long scan is pending, and the schedule may
be off or daily, so uploads kept a desktop's old folder template or proxy size.
- Every schedule change and run, a skipped run included, is published as a
scheduleChanged event. The Scheduled tab reloads on it, so skipped runs, next-run moves
and other administrators' edits show without waiting for a job.
- The Scheduled tab still draws when the schedule a job links to, or an expanded one, no
longer exists: its runs are dropped instead of failing the whole load.
- Every time on the Scheduled tab (next run, last result, runs) is in the server's time
zone, as its "Times in" line says.
- Audit details name a system schedule after its key (system:<key> · name · ...). The
dashboard and the Logs page show it by its localized name and the recurrence code in
words, as the Scheduled tab does. Older entries keep their recorded name.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c20f573d0bdf1cdcf3a86e9702ac76a4bf9508d9)
Owner review 2, phase 2 review findings (scheduler core).
- Log.Write caught only IOException. Microsoft.Extensions.Logging wraps
provider failures in an AggregateException, so a log line that could not
be written (in tests: the process-wide sink of a stopped server whose log
folder was gone) escaped JobEngine.RunAsync's catch before the failure was
stored: the job stayed running and the worker faulted. This was the cause
of the intermittent JobApiTests/ArchiveModuleTests failures. Log.Write now
drops any non-fatal sink failure, TeeLogSink keeps a line from the other
sinks, FileLogSink drops a line it cannot write and reopens the file at the
next one, and LoggerSink drops what the providers throw. The scheduler's
loop relies on the same guarantee.
- The daily backup loop (RunDailyAsync, IsDue, Interval, CheckInterval) had
no caller since the index-backup schedule replaced it; it is removed and
the DatabaseBackups summary describes the schedule.
- The first copy after the upgrade no longer waits a day (or for 03:00):
SystemSchedule.LastDone seeds a new row due at once when its work was last
done a period or more before, and both hosts pass the newest copy in the
backups folder for index-backup.
- Back up now (Settings and Archive), the copy kept before a restore and a
backup job that keeps fewer prune to the largest Copies kept of the backup
schedules (DatabaseBackups.KeptAsync), not a fixed three. The four
tooltips that promised three daily copies are reworded (en, it) and their
stale translations deleted.
- New tests for the scheduler loop itself: a tick, Wake, a pass that threw,
and dispose during a pass.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit c5ad0c4c3f636129afe5dd1ce039185516da5621)
Settings › Logs › Keep audit showed ServerOptions.AuditRetentionDays, a second
copy of the audit clean-up schedule's age limit. Edits made on Jobs › Scheduled
never reached it, so the panel could say "kept forever" while entries were
being deleted every night. Saving 0 there then changed nothing, because the
endpoint only compared against the stale option value.
- GET and PUT /server/settings now report the schedule's limit in force (0
while the schedule is off). Saving compares against that value. A value sent
back unchanged leaves the server.json reset default and the env lock alone. A
new value sets the schedule and becomes the reset default.
- ApplyAgeAsync also turns the schedule on when it already holds the days but
is off.
- CHRONOS_AUDIT_RETENTION_DAYS is now applied before the scheduler's first
pass, through a new Scheduler.StartAsync overload with a beforeFirstPass hook.
Before, a missed 04:30 run was caught up at start with the stale days, which
could delete entries the variable says to keep. While the variable fixes a
limit above 0, turning the schedule off is a 409 setting_locked.
- Corrected the comments in SchedulerHost, ServerOptions, ServerSettingsStore,
LogSettingsDto, the header of settings.js and ARCHITECTURE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 490ed286e9f32745174b13b1963d6ec91955196b)
The desktop opened its log files with the default limits and wrote its first
line, which prunes, before Settings › Advanced › Logs were applied. Every start,
and every launch that only hands its file to the running Chronos, deleted logs
older than 14 days and cut the folder to 1 GB whatever the user kept.
AppLogging.Open now builds the sink from the stored settings before that line;
the settings are read again once the launch owns the data folder.
A total below one file deleted each finished file as the next one opened. The
rule now lives in LogFileOptions.TotalBelowFile: the server keeps refusing it,
the desktop raises the total to the file size and its rows no longer offer the
combination.
The desktop log rows threw on negative sizes from an imported or hand-edited
file and showed raw values the files never got; they now show the applied ones.
Upgraded Unraid and compose installs keep CHRONOS_LOG_LEVEL=Information, which
locks both levels. The lock stays; the server now reports which variable fixes
each locked setting (LockedBy), so the panel's tooltip names it exactly and says
to remove it to change the value there. The releases README tells upgraders.
The former-constructor log test no longer fails across midnight UTC.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 8ba7162bd5926d34c5ec4e40e2a2dad063ee19c3)
Settle what the R10 scheduler and R11 log packages left open when they were
integrated (owner review 2, phase 2).
- Audit retention has one source of truth, the audit-cleanup schedule's age
limit. AuditRetentionDays defaults to 0 (the audit log is kept forever, so
an upgrade deletes nothing; the schedule is seeded off) and accepts 0-3650,
what a schedule's age limit takes. Saving Settings › Logs › Keep audit sets
the schedule's limit (on with a limit, off at 0) without a restart;
CHRONOS_AUDIT_RETENTION_DAYS locks it and Reset goes back to it.
- Both hosts scan right after start again, as their polling did: the server
after the scheduler starts, the desktop once the archive was reopened and
again when an unplugged one is back. Scheduler.RunSystemNowAsync runs the
archive-scan schedule when it is enabled and has not run since the start,
and skips while its scan is pending.
- Desktop scans follow Settings › Analysis › After a scan at every run: a scan
schedule without its own deep parameter asks the host
(IScheduleHost.DeepAnalysisAfterScan), the archive-scan schedule no longer
freezes the setting, and the editor offers deep only for analyses, so the
setting's tooltip stays true.
- The server's upload clean-up runs every 6 hours instead of every 30
minutes, to keep the job history readable; idle uploads still expire after
UploadRetentionHours.
- The Unraid template and docker-compose leave CHRONOS_LOG_LEVEL empty or
commented out, and say that setting it locks both log levels, so the admin
panel can change them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 2, R10 on the desktop: every timer that queued work out of
sight is now a visible, editable schedule of this PC.
- DesktopScheduleHost implements IScheduleHost: the PC's time zone, the
archive at Settings › Archive's folder (refreshed from archive.json,
none while it is offline), and three system schedules: archive-scan
(every:<ScanIntervalMinutes>m, seeded once from the old setting, no
catch-up), index-backup (every day with catch-up, replacing
DatabaseBackups.RunDailyAsync) and housekeeping (daily 04:00 with
catch-up: job history 90 days and the new cache-trim step).
- AppServices starts the Scheduler after the engine, once the archive was
reopened; an unplugged archive is looked for every minute and the
scheduler woken when it is back. The rescan loop and the daily backup
loop are gone; ApplyJobSettings wakes the scheduler.
- CacheStore.Trim brings the cache to Settings › Storage › Cache limit,
oldest files first, skipping files in use and the proxies, render-node
and server-import folders; CacheTrimStep runs it as a clean-up step.
- Jobs gets a Queue | Scheduled segmented control. Scheduled lists the
schedules (switch, name, action, when, next run, last result) with Run
now, Edit, Reset (system) or Delete (user's, confirmed), the selected
schedule's last runs with Show in queue, and an in-window editor that
checks every field with the scheduler's limits. Jobs a schedule queued
carry a "Scheduled" pill; the history line follows the housekeeping's
job-history days.
- JobNotices: a scheduled background run raises a toast only when it
fails (upkeep stays silent).
- Settings › Archive › Rescan every is removed; ScanIntervalMinutes stays
only as the seed. Strings in en and it; the others are retranslated.
- The capture shows jobs-scheduled and jobs-schedule-editor on a stopped
scheduler clock with sample schedules.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit e25d812feb3f417cb9251c748c29e8035fd9b03c)
Owner review 2, R10: nothing may run out of sight, so every timer the server
ran becomes a system schedule the admin panel shows and manages, and
administrators create their own.
- SchedulerHost runs the shared Scheduler on the job engine (started after
JobEngineHost, stopped before it); ServerScheduleHost gives it the
container's time zone (UTC with a warning when TZ is unknown), the archive
refreshed from archive.json at every run (what ArchivePolling did), the
clean-up steps and the system schedules: archive-scan every 10 minutes
(no catch-up, also run once at start like the polling), upload-cleanup
every 30 minutes, index-backup at 03:00 (SQLite only), housekeeping (job
history) at 04:00 and audit-cleanup at 04:30.
- ArchivePolling and DatabaseBackupService are gone; UploadMaintenance only
recovers commits at start, its sweep is the "uploads" clean-up step.
- /api/v1/schedules (ManageArchive, audited): list with actions and time
zone, create, PUT/PATCH, delete (409 schedule_system), run now (409
schedule_pending), reset (409 schedule_no_defaults), runs paged by cursor;
invalid fields are 400 invalid_schedule naming the field.
- CHRONOS_AUDIT_RETENTION_DAYS (AuditRetentionDays, default 365) seeds the
audit clean-up; set by the environment it is applied at every start and
locked. Job history leaves Settings: it is the housekeeping schedule's age
limit, and the setting is what a reset restores.
- Admin panel: Jobs has Queue and Scheduled tabs; schedules with when (in
the panel's language and the server's zone), next run, last result, a
switch, Run now, Edit, Delete or Reset, their runs linking to the jobs, and
a side panel for the action, recurrence and parameters; job rows a
schedule queued carry a Scheduled pill. Strings in en and it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit 808ce94ae29e3bf4522cb4d40dfd76d4f8529c64)
Owner review 2, R10: every timer that queues work becomes a visible schedule,
so the server and the desktop need one shared engine to run them.
- Migration 0007: schedules table (system rows keyed by system_key) and
jobs.schedule_id; Job.ScheduleId, JobDto.ScheduleId, JobRepository
HasPendingAsync / ListPendingTargetsAsync / ListByScheduleAsync.
- ScheduleRepository: seeding that keeps user edits, reset, compare-and-set
claim of a run (one winner across processes), outcomes.
- Scheduling: in-house recurrence (every/daily/weekly/monthly, DST gap moves
forward, ambiguous time runs once), ScheduleActions resolving scan, verify,
thumbnails, proxies, analysis, maintenance, backup, cleanup, duplicates and
orphans into archive jobs, IScheduleHost, and the Scheduler loop (catch-up,
clock going back, run now, CRUD as API v1 DTOs).
- New job kinds Backup (16) and Cleanup (17) with handlers, shared clean-up
steps (job history, audit log, trash report that never deletes) and host
steps through ArchiveServiceOptions; read-only Duplicates and Orphans report
handlers, so the server can run those kinds too.
- JobEngine no longer purges history at start: the housekeeping schedule's
job-history step does; JobEngine.CanRun and an EnqueueAsync with scheduleId.
- Protocol DTOs for schedules; job kind names in en and it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit eb0edd2483a493db7c6945d5b494461cabb2a4ad)
Owner review 2, R11 asked for more log settings. The file sink now writes daily or
hourly files, continues a full file in numbered parts and prunes by age and by the
total size (never the file being written); its options change while it runs.
Server: the file and console levels are separate and read by the logging filters
at every line, so the admin panel's new Logs group applies without a restart; the
engine's level follows the lower of the two. This also fixes a bug: the file logger
was fixed at Information, so CHRONOS_LOG_LEVEL=Debug or Trace never reached the
files. New variables CHRONOS_LOG_CONSOLE_LEVEL, CHRONOS_LOG_RETENTION_DAYS,
CHRONOS_LOG_MAX_FILE_MB, CHRONOS_LOG_MAX_TOTAL_MB, CHRONOS_LOG_ROTATION,
CHRONOS_AUDIT_RETENTION_DAYS and CHRONOS_DIAGNOSTICS_LOG_MB lock their settings like
the others; the diagnostics zip keeps the configured share of each log.
Desktop: Settings > Advanced gains Log level, Keep logs, File size, Logs total,
Rotation and Diagnostics logs, applied at every save; Advanced's Reset section
restores them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
(cherry picked from commit cc875784e4952ee0e4c807b9d9c18496d3d5a8c3)
- :latest follows the highest stable release, or the highest pre-release while none is stable (Chronos.Tools release-channels); bad tags are refused before anything is built.
- Unraid: CHRONOS_SPACE_PATH and the template's Array view show the array's free space; the write volume (cache) is shown apart; completions check the archive volume (507).
- Settings is a gear, docked at the foot of the admin sidebar; About is the last part of Settings on the desktop and the panel.
- Import > Folder > Whole folder: one sequence per format (desktop only).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
Gitea writes a release's html_url and browser_download_url with its ROOT_URL,
which on the owner's server is the plain-http LAN address
http://192.168.30.23:3000. The update check accepts only https links, so it
ignored v0.1.0-rc.1 entirely. The page and download links now come from
ChronosReleasesUrl, the address the build names for its users; only the
tags, file names and sizes are read from Gitea's answer.
The lease renewal test's timer periods follow TestTiming too: on the shared
CI host a 100 ms renewal timer came 700 ms late once.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
The owner renamed the product and moved the repository to the self-hosted
Gitea (https://gitea.encke-hake.ts.net/BalboSoft/Chronos) for more control,
and asked for Actions and a first automatic release with the server package
and the Windows exe (docs/requests/2026-10-23-chronos-gitea.md).
- Chronos everywhere: a byte-exact rename of contents and paths, then a
per-language review of the forms the old name's ending had dictated.
- Gitea instead of GitHub: the update check, licence, issue and support
links read ChronosReleasesUrl; the update check takes the highest stable
version, offers a pre-release build its final release and reports a
repository it cannot see as a failed check. EULA, security policy and
Gitea issue forms live at the repository root.
- Gitea Actions for the Linux act_runner (.gitea/workflows): CI, release,
nightly image and performance gates in the .NET SDK container with git
checkout and the system SQLite. The release cross-compiles the Windows
programs, checks their icon, version and DPI manifest, packs installers
and zips, publishes the Gitea release and pushes the server image
(REGISTRY_TOKEN). Windows-only tests run in an opt-in job on a Windows
runner (WINDOWS_RUNNER).
- New Chronos.Tools commands: zip, gitea-release, postgres-ci (replaces the
docker-exec script, which Gitea's service containers do not allow; the
throw-away server runs without durability) and pe-check.
- Timed tests take their budget from TestTiming (CHRONOS_TEST_TIME_FACTOR,
3 on the shared runner; the weekly performance gates keep theirs).
BREAKING CHANGE: programs, settings, data folders, file types, environment
variables and the Docker image use the new name; nothing is migrated from
Titano, which never had a release.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Alberto Balbo <alberto.balbo.96@gmail.com>
- Implement tests for picker behavior, including loading sequences, searching, and handling empty libraries.
- Validate sequence opening via Enter key and double-click actions.
- Ensure proper handling of unsaved edits and sequence deletion scenarios.
- Verify accessibility features for picker rows across different languages.
- Introduce a dialog counting mechanism to manage unsaved edit confirmations.
Owner review 1, phase 3a (docs/requests/2026-10-15-owner-review-1.md, R1).
The desktop rail is 200 px wide, so the section names fit in every
language, and collapses to 48 px of icons with its ≡ button or Ctrl+B.
Collapsed, each icon's tooltip names its section before saying what it is
for, while screen readers keep the name and the description. The choice is
written to the settings file the moment it changes (nothing else restarts)
and survives Settings › Reset all and Import; Ctrl+B waits behind the
first-run dialog like Ctrl+1…6, and a held key toggles once.
The admin panel's sidebar is 256 px and collapses to icons the same way,
with its own ≡ button or Ctrl+B (on the physical key where the layout's B
types no Latin letter, so Cyrillic, Greek, Hebrew and Arabic layouts work).
The choice is kept in the browser, for the page when the browser refuses
storage, and the tables fit their columns again after each toggle. At
900 px and below it stays the top bar and Ctrl+B stays the browser's.
The wider rail leaves 49-72 px less for every screen at the 1200 px
minimum. Six adversarial review rounds found what that cut, and in every
shipped language no action is cut off now: the Jobs columns share their
width (Target and Progress give way first, Kind/Where/State capped on wide
windows), the editor's preview tools take a second line, a server job's
Cancel has its own header column, the Archive tree keeps a year's label,
the Import rows and result, the certificates and cache rows and the frame
table fit. Headers, titles and cells that may be shortened end in an
ellipsis and show their text in their tooltip; state tooltips start with
the state, and their explanations were reworded not to repeat it (a queued
job "waits for its turn", jobs running one at a time). The crop-result
tool sits beside Crop mask, disabled with its reason while the mask is
off. Tests check these rows in all 38 languages at 1200 px; the App test
program now shuts WPF down in order, so its exit no longer crashes after
every test passed.
Phase 3 lands as two commits: R7 (the Edit section) edits the same shell
files and follows. Also updates BRIEF (12.1, 14.8, 24), DECISIONS,
CHANGELOG, STATUS, the request file, DESIGN and the mockups; every new or
reworded string is in all 38 languages.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 2 (docs/requests/2026-10-15-owner-review-1.md, R2).
Jobs now run one at a time on the desktop and on the server. Parallelism
(Settings > Rendering, TITANO_PARALLELISM) is how many photos the running
job processes at once: thumbnail and proxy passes draw that many photos
together and still write the pack and checkpoints in frame order, decode
tiers are probed that many at a time, the deep analysis measures that many
frames and a render decodes that many ahead. Wherever originals are
developed whole (TIFF, PNG, RAW without a usable preview), fewer run at
once within the memory budget, which the running job now has whole; the
server's frame window is sized to the host instead of 1 GiB.
A new job waits its turn and pausing the running job starts the next one.
An optional priority queue gives each job kind a level (renders, imports
and downloads high, verifies and proxies low by default): a queued job of
a higher level pauses the running one without asking, and that job goes
back to the queue with its checkpoint and resumes by itself afterwards.
Jobs of the same level, and a job's own follow-ups, never interrupt it.
The Jobs screen and the admin panel show the parallelism and the queue;
Settings > Rendering and the admin panel's Settings set them, at once.
TITANO_WORKERS and the Workers key of server.json still set the
parallelism (1 to 64, with a warning at start for the variable).
Titano.Tools gains i18n prune, which removed the renamed keys from the 36
machine-translated languages; the new strings are translated in all 38.
Found while testing: uploads and imports failed when a pass read the
sidecar while they wrote it (atomic writes now retry the rename while a
reader holds the file, and never for a read-only one), and taking a lease
just released while another process read it failed on Windows (the create
now waits for the reader). Five adversarial review rounds checked the
phase before this commit.
Also updates BRIEF (12.8, 14.6, 14.8, 14.9, 24), DECISIONS, CHANGELOG,
ARCHITECTURE, STATUS, the request file and the compose/Unraid templates.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Owner review 1, phase 1 (docs/requests/2026-10-15-owner-review-1.md).
Thumbnail and proxy jobs over several sequences counted sequences while
they checkpointed inside one: the rate decayed until the time left
overflowed TimeSpan, the job failed while publishing progress and again
while saving it, and stayed Running. The throughput is now seeded by the
first window with progress, the time left is bounded (JobEta), saving
progress never throws, image passes count frames, and job speeds use the
right unit (bytes for verify and import).
The debugger stops in WicDecoderProvider.cs when presets changed were
cancelled preview decodes leaving synchronous thread-pool delegates; the
editor's sources, LatestRunner and the render node's proxy task now keep
them in their own tasks, and a cancellation is never an unreadable frame.
GoPro DNGs converted by Adobe software were classified GPR and read only
through their 8-bit preview, and Windows' preview-only DNG decoder was
reported as a native decode. A DNG is GPR only when its raw image is
VC-5, WIC decodes RAW only through the Raw Image Extension and never DNG,
analyses and previews take an adequate embedded preview by choice while
renders develop natively, and frames already indexed as GPR are
reclassified by the next light analysis.
Also records the owner's request (docs/requests), the BRIEF amendments
(§8.1, §8.2, new §24), DECISIONS, CHANGELOG, STATUS and ARCHITECTURE.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The orphans fix and scans treated a folder whose only new photo could not be
read yet (held open, no permission, an offline placeholder) as changed: the
sidecar was rewritten, the covering flags cleared and analyses queued again at
every click. SequenceAdopter.Reconcile now returns null when it indexed nothing
and changed no flag, as its contract says.
A deep pass counted as current by frames version alone, so a pass whose verdict
a proxy made stale overwrote the report a later pass made from the proxies,
then dropped the deep status. It now counts as current only when its report
describes the frames as they are, and otherwise replaces only a saved report
that does not describe them either.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A desktop scan queues a background deep analysis of the sequences whose
frames it changed when Settings > Analysis > After a scan is on; photos the
Archive screen's orphans fix indexed got only the light analysis, which then
dropped the deep status. ArchiveService.ReconcileAsync takes that setting
and queues the deep analysis too, at background priority. A follow-up is
left out when a queued job of its kind already covers the sequence, whatever
else that job targets, as the scan's follow-ups check.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A deep pass overtaken by a frames change that keeps the frame count, with a
light analysis queued, leaves an analysis.json of that count in place rather
than save its own. It then still recorded its own report: the deep status,
summary, warning count and Auto values described a report that is not on
disk, and the queued light analysis kept that summary until the next deep
pass. SaveReport now says whether it saved; when it did not, the pass reads
the saved report as a light analysis would and records that one.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
Each index of a shared archive bumps a sidecar put back behind its own row
to one version past that row, which can be the version another index holds
for other frames (a desktop rebuilding a damaged sidecar while the server is
one upload ahead). That index then took the sidecar's frames as unchanged:
it kept the project's positions and what covered the frames, and clients and
editors holding that version saw nothing. When the versions match, a scan
now also compares the row's frame ids and order with the sidecar's; other
frames are read again under the lease and written one version past the row.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The Archive screen's orphans fix indexed photos copied in by hand but left
AnalyzedLight, ThumbsBuilt and ProxiesBuilt set and recorded the folder's
stamps, so no scan came back to it and the light analysis was never redone:
Auto values, warnings and preview-only tiers stayed those of the old frames.
It now clears the three flags in the sidecar and the row as a scan's
reconcile does, and queues the light analysis on the host's engine (on a
server, the thumbnails and proxies too).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A deep pass saved analysis.json as soon as it finished, before it checked
that its frames were still the sequence's. A pass overtaken by an upload, or
by another Titano sharing the archive, replaced the report a later pass had
made of the frames as they are: the report endpoint answered 404 and the
next light analysis dropped that pass's deep status. The report now waits in
memory and is saved under the sequence lock, when its frames are current or
the saved report describes the frames as they are no better; the checkpoint
is deleted only then.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
Each tag upsert locks its row until commit, and tags were written in the
order the caller listed them. A PATCH listing them in another order than
an upload, a scan or another edit of a sequence sharing two of them could
lock the rows in opposite orders, and PostgreSQL aborted one writer with a
deadlock that nothing retries. Tags are now written in the order of their
keys, and a set the sequence already carries is not written again.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
ApplyLocallyAsync recorded the folder's scan stamps unconditionally after
writing the server's title, tags, rating or notes into the sidecar. Photos
another process (a desktop sharing this archive) had listed there since
this index last synced the folder then stayed out of the index until the
folder changed again, and the row's frames version stayed behind the
sidecar's, so analyses here recorded nothing for the sequence meanwhile.
It now asks ArchiveIndexer.InStepAsync before its sidecar write, as the
other partial writers do, and records the stamps only when that held.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
An analysis compared only this host's index row with the frames version it
read at its start. On a desktop sharing a server's archive, the server's
upload bumps only the shared sidecar until the desktop's next scan, and a
desktop scan clears nothing. A desktop pass that recorded in that window
wrote Auto values and statuses for the old frame count over the server's
analysis in the shared project.json and sidecar, and nothing analysed the
photos again.
Under the sequence lock the analyser now reads the sidecar first. When its
frames version is not the row's, the photos changed in another process and
this index does not hold them yet: the pass records nothing, logs
Advisor.Log.FramesChangedElsewhere and queues nothing, since a light
analysis here would read the same index. The process that changed them
analyses them, and this host's next scan indexes them (a server's scan
then queues their analysis). A moved row still queues a light analysis
unless one is queued, in which case the pass records as before.
Tests cover the shared-archive case with a second index and engine, and
the queued-light escape on a one-worker engine.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
FrameRepository.UpdateLightStatsAsync updated every frame of a sequence
in batches without locking the sequence row. On PostgreSQL a scan's or
rebuild's sync holds the row and rewrites every frame in its own order,
so a deep analysis writing its statistics at the same time could hold
some frames while waiting for others the sync held, and PostgreSQL
aborted one of the two jobs with a deadlock.
On PostgreSQL the method now locks the rows of its frames' sequences
first, in the same transaction, like every other writer of a sequence's
frames. SQLite's write lock already serialises writers.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
An upload batch that found the folder out of step resynced the sequence
from its sidecar and recorded the photo directory's current stamp. When
the photo directory had changed since the last scan (a photo copied into
originals/ by hand or by another process), that stamp hid the change from
every incremental scan, so only a full scan or the orphans check indexed
the photo.
The batch now asks ArchiveIndexer.PhotosChangedAsync under the lease
before it files its photos. When the photo directory had changed, the
resync records the photo stamp the index held before (none when none was
recorded), so the next incremental scan still reconciles the folder.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A proxy download marked the cache filled whenever the server's sequence had
ProxiesBuilt, even when frames added since the server's last proxy pass got
a thumbnail or nothing (the flag offers their proxies, the endpoints answer
404 until the pass draws them), and frames without any cached file were not
counted at all. The agent never compared such a cache again, so the editor
kept thumbnails or blank frames until the frames changed.
The cache now counts as filled only when every frame, missing or damaged
ones aside, is cached as a proxy. On a server with ProxiesBuilt, a download
that left stand-ins is queued again once the server's update time moves, so
a frame the server cannot serve yet is not fetched at every refresh.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A light or deep analysis read its frames at the start and, under the
sequence lock, recorded AnalyzedLight, the warning count and the advisor's
Auto values for them whatever happened meanwhile. Frames added by an upload,
an import or a scan's reconcile then kept advice and warnings counted on the
old frame count, over a newer light analysis, and scans never queued another
one because AnalyzedLight was set again.
Under the lock the analysis now compares the row's frames version with the
one it read. When it moved and no light analysis is queued for the
sequence, it records nothing (a deep pass keeps only analysis.json and its
per-frame measurements), and the job logs it and queues a light analysis of
the frames as they are. A queued light analysis replaces what the pass
records, as for image passes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
ArchiveIngest appended the new frame rows and recorded the folder's stamps
whenever the batch appended at the end and the frame count matched, even
when a desktop sharing the archive had changed the sidecar alone (a
verify's hashes and Missing/Corrupt flags, decode tiers, duplicates, a
title). The server's frames then never got those changes, and the stamps
hid them from every incremental scan until a full scan.
A batch now asks ArchiveIndexer.InStepAsync under the lease, before it
changes the folder, and appends only when the index held the folder as it
was; otherwise it syncs the whole row and every frame from the sidecar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
The scan's plain branch indexed a sidecar read without the lease. When an
upload or a partial writer (decode tiers, a verify) committed between that
read and the scan's transaction, the scan wrote its older copy over the
newer row and frames (dropping the uploaded frame rows), then recorded
the folder's current stamps, so incremental scans skipped the regression.
Under the row lock, SyncAsync now refuses an unleased read when the
sidecar no longer has the stamp the scan listed or the row holds another
frames version, and the scan reads the sidecar again under the lease. An
unleased sync records the stamps it was checked against, and the index
snapshot files each sidecar under the stamp it was read at. Under the
lease, a sidecar behind the locked row (an older copy put back) is
written again one frames version past the row, so the version never goes
back. Statuses cleared in this host's row only (Uncovered) now pass as a
parameter, so that rewrite never clears them in the shared sidecar.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC
A verify's flush replaced every flag of a pending frame, in the sidecar
and the index, with the flags it computed from the frame as read without
the lease, possibly hours earlier. A preview-only or undecodable tier, a
duplicate flag or a repair recorded meanwhile was reverted, and a photo
an upload repaired during the run was flagged missing again, so the next
copy moved the good file aside.
Under the lease the flush now merges only Missing and Corrupt into the
frame's current flags, and the index sets and clears only those bits with
the hash, after locking the sequence row. A check whose sidecar record or
file (size and modification time taken before it was read) changed since
is left for the next verify.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012iLMBNwBE2GnphAsu4cjaC