Owner review 5 (2026-11-15), released as v1.1.0. Request, answers and plan: docs/requests/2026-11-15-owner-review-5.md.
#64 One setup: a single Chronos-Setup installs and updates Chronos Desktop and/or Chronos Uploader. Chronos Server is Docker only. A 1.0 Windows Server install is shown as "no longer offered" and can be removed, as a planned, explicit action. The Uploader checks for updates and downloads the single setup. The update code is shared in Chronos.Core/Updates and Chronos.Ui/Updates.
#65 Progress detail: jobs report the step, photo x of y, sequence n of m, the rate and the time left. Reports are published at most twice a second, through a shared gate, and migration 0011 stores the detail. The detail appears:
in the desktop's Jobs, job bar, Archive and editor;
in the admin panel;
in the desktop's Server section, which lists the connected server's jobs, with pause and cancel only for accounts that have that right.
#66 Per-server homes: each server gets a stable id. Cache, workspace and originals archive are kept under servers\<id>, apart from local. The 1.0 workspace and cache are sorted into this layout at the first start. Sync links are re-keyed to the server id.
#67 Desktop as server: Settings › Server › Share this library hosts the server engine in-process over the desktop's own archive and index. Chronos.Server becomes a library, and Chronos.Server.Host is the Docker exe. Shared mode exposes only client jobs on the shared archive. While sharing, closing the window hides Chronos to the tray. The desktop warns when the 1.0 Windows service is still installed. The Windows service hosting is removed.
One review round: 15 findings, all fixed. Strings are in all 38 languages, and the screenshot baselines are updated.
Checks on the PC:
build: 0 warnings;
tests green for Core, Data, Server, Tools, Core.Windows and App (App with the usual exclusions);
i18n check, xaml-lint, package-guard and format all clean.
Not run on the PC: the Windows-only smoke tests, installer-test.ps1 and the release dry run.
Owner review 5 (2026-11-15), released as `v1.1.0`. Request, answers and plan: `docs/requests/2026-11-15-owner-review-5.md`.
- **#64 One setup:** a single `Chronos-Setup` installs and updates Chronos Desktop and/or Chronos Uploader. Chronos Server is Docker only. A 1.0 Windows Server install is shown as "no longer offered" and can be removed, as a planned, explicit action. The Uploader checks for updates and downloads the single setup. The update code is shared in `Chronos.Core/Updates` and `Chronos.Ui/Updates`.
- **#65 Progress detail:** jobs report the step, photo x of y, sequence n of m, the rate and the time left. Reports are published at most twice a second, through a shared gate, and migration 0011 stores the detail. The detail appears:
- in the desktop's Jobs, job bar, Archive and editor;
- in the admin panel;
- in the desktop's Server section, which lists the connected server's jobs, with pause and cancel only for accounts that have that right.
- **#66 Per-server homes:** each server gets a stable id. Cache, workspace and originals archive are kept under `servers\<id>`, apart from `local`. The 1.0 workspace and cache are sorted into this layout at the first start. Sync links are re-keyed to the server id.
- **#67 Desktop as server:** Settings › Server › *Share this library* hosts the server engine in-process over the desktop's own archive and index. `Chronos.Server` becomes a library, and `Chronos.Server.Host` is the Docker exe. Shared mode exposes only client jobs on the shared archive. While sharing, closing the window hides Chronos to the tray. The desktop warns when the 1.0 Windows service is still installed. The Windows service hosting is removed.
- One review round: 15 findings, all fixed. Strings are in all 38 languages, and the screenshot baselines are updated.
Checks on the PC:
- build: 0 warnings;
- tests green for Core, Data, Server, Tools, Core.Windows and App (App with the usual exclusions);
- i18n check, xaml-lint, package-guard and format all clean.
Not run on the PC: the Windows-only smoke tests, `installer-test.ps1` and the release dry run.
Follow-ups (not in this PR):
- firewall status row;
- Change…/Forget on known servers;
- the LAN beacon announcing the server id;
- docs/ui mockups for the new screens.
Closes #64
Closes #65
Closes #66
Closes #67
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Alby96
added this to the v1.1.0 milestone 2026-11-15 17:02:40 +01:00
Move UpdateCheck, UpdateDownload and ProductLinks to Chronos.Core/Updates and
UpdateFlow to Chronos.Ui/Updates, so the Uploader can reuse the update check
(#64) and the check and download tests run on Linux in Core.Tests. No
behaviour change: only namespaces and usings moved. Record owner review 5
(request, interpretation R1-R5, answers Q1-Q3, the v1.1.0 phase).
Refs #64
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Uploader had no update check, so an Uploader-only install never heard of
a new version. Its settings panel gains an Updates row driven by the shared
UpdateFlow: Check on start (opt-out, on for 1.0 settings files), Check now,
Download (the single Chronos setup, or the portable zip of a portable copy,
verified against the release's SHA256SUMS) and Show setup (reveals the
verified file in Explorer; the user runs it). The start-up check is skipped
when Chronos.exe sits beside the Uploader, because the desktop's own notice
covers the same setup; Check now still works there. A newer release found on
start is offered in a toast with Download as its action. The capture scene
shows the notice with a sample release.
Refs #64
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Mass passes need to say what they do now (photo x of y, sequence n of m) without
slowing down. This adds the contract and the engine side; handlers and displays
follow in their own parcels.
- Core: JobDetail (step, item, item x of y, part n of m with unit), JobStep and
JobPartUnit appended-only and stored by kebab name; Job.Detail.
- Protocol: JobDetailDto, appended as JobDto.Detail, JobProgressEvent.Detail and
NodeProgress.Detail, so older peers ignore it and newer ones fall back.
- Data: JobContext keeps a detail across reports (ReportAsync with a detail,
ReportItemAsync without allocating, CheckpointAsync with a detail) and publishes
at most once per ProgressInterval (500 ms on the engine's TimeProvider), at once
for the first report, a new step or a completed count; a dropped report costs no
allocation or lock, and the persist that falls due publishes what it saves.
Persist stays at most every 5 s. JobWire maps steps, units and details; an
unknown name reads as none.
- Migration 0011 adds jobs.progress_detail (nullable JSON text); an unreadable
cell reads as no detail. Lists return it.
- Server: ProgressGate (500 ms per job, step-change and completion bypass)
shared by the engine host and render nodes; node details are stored and
broadcast, an older node without one still works.
Refs #65
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Chronos Server now ships as a Docker image only, so the Windows setup no
longer offers it and the separate Uploader setup goes: one setup installs,
updates, adds and removes Chronos Desktop and Chronos Uploader in place.
- Install log format 2 records each component's files, shortcuts, version
and SHA-256; format 1 logs (1.0) are still read. A file of a removed
program that changed since setup installed it is kept, never deleted.
- A Chronos Server 1.0 for Windows installed by 1.0 is retained as "no
longer offered": its files and service are untouched until the user
unticks it or explicit /COMPONENTS leave it out; then it is removed with
its service. A format 1 log keeps every file the payload does not know.
- The separate 1.0 Chronos Uploader product is replaced: the Uploader is
preselected, its sign-in entry moves to the new copy (Task Manager state
kept), its shortcut is handed over and the old product is uninstalled.
An all-users copy under a per-user install stays and is said so.
- The setup window shows the dry-run plan (Changes: adds, removes,
replaces) before Update; with every program unticked the primary action
becomes Uninstall. /COMPONENTS=Desktop names the desktop app.
- pack-installer refuses Server (--legacy packs a 1.0 one for the CI test);
release.yml publishes only Chronos-Setup-<v>.exe and the portable zip;
the installer test covers add/remove in place, the Uploader replacement
and the retained Server.
Refs #64
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The desktop keyed every server by the address it was reached at, so one
NAS reached by name and by IP, or after an address change, looked like two
servers, and all servers shared one workspace and one cache. Each server
now announces a stable id, and the desktop's folders are sorted into one
home per server, so that every server can have its own archive of
downloaded originals (or5 answers Q1).
- The server makes a Guid v7 once, keeps it as the app setting server.id
(so it survives restarts and restores, on SQLite and Postgres) and
announces it as ServerInfo.ServerId. Older clients ignore the field, and
older servers read as null.
- ServerIdentity keys a server as id:<N> when it announces an id, and by
its address otherwise. Address keys are kept as aliases.
- HomeFolders names the homes: local, servers/<id> or
servers/addr-<hash16>. The hash equals the 1.0 proxy cache folder name.
It also names the per-server originals archive root.
- WorkspaceHomes splits the workspace into one format-1 store per home
under a format-2 parent manifest, which 1.0 refuses. A 1.0 workspace
stays one store until it is sorted.
- HomeLayoutMigration plans as a dry run and applies through a journal:
- only same-folder renames, each checked by inventory;
- a clash keeps the copy saved last and sends the other to the trash;
- it resumes after a crash at any step;
- it skips leased projects;
- it defers an offline workspace or one being moved, while the cache
part still runs.
- RekeyAsync moves an alias home to the id home: whole folders, or
project-by-project merges. It also rewrites working states under their
lease, and moves sync_links (the newer row wins a clash).
- ProxyCache, the job root resolver, WorkspaceMover and WorkspaceCleaner
understand the split layout. The new layout is opt-in through
SyncOptions.ServersDirectory, so the app sees no change until it is
wired.
Refs #66
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The job list showed a bar and a free-text line that each handler worded
its own way. Each handler now reports its step, the item it is on, photo
x of y and sequence/folder/output/step n of m through the P2.1 JobContext
detail. Clients can word and lay that out themselves, and the 2/s
throttle keeps the cost low: counts within a step go through
ReportItemAsync, which allocates nothing.
- scan: List, then Index (folder n of m, photo x of y as an adopted or
reconciled folder is read) or Check, then FollowUps
- verify, thumbs, proxies, deep analysis: photo x of y of sequence n of m;
light analysis: sequence n of m; a thumbnail/proxy checkpoint carries
the frame count it saves
- convert: Verify (resume), Convert photo x of y, Replace; reorganize:
step n of m with the title; import: the file being copied, photo x of y
- maintenance: the step key, step n of 5, then Check; duplicates, orphans
and backup run with no count; cleanup names step n of m; empty trash:
entry n of m
- render (local, workspace, render node): Analyse, Encode (frames of the
last output, output n of m in a batch), Verify; sync, video copy,
workspace copy/send/move: Upload/Download/CopyProxy/CopyOriginal/
CopyVideo/Reorganize with their items and counts
The detail carries keys and names only, never localized text. The
existing Message strings stay for clients that still show them.
Refs #65
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A running job now says what it does now: "Verifying photo 812 of 2,400 · Harbour sunset · sequence 3 of 41". A paused or
failed job says where it stopped. The line appears in the Jobs table under the target, in the job bar (at most 60
characters, the item dropped first, the bar text also its tooltip), in the Archive's recent maintenance (refreshed at
most twice a second), in the editor's server-job line and in the sync tooltip. Byte jobs now count sizes in the bar.
While connected, the Server section lists the server's running and paused jobs, live through the jobs API and the
jobProgress events. Pause, Resume and Cancel are offered only to an account that manages the archive, which is what
the server requires to act on someone else's job; for any other account the list is read-only. The list hides while
nothing runs, and the capture gains a server-jobs scene.
The admin panel's Jobs page and dashboard show the same line under the target and update it with every progress event.
The steps, parts and sub-steps are in English and Italian, and an unknown step shows its counts only.
Refs #65
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The desktop now uses the per-home layout from P3.1: each home keeps its
own projects, proxies and originals, and a server is known by its id
whichever address reaches it.
- Settings keep the known servers (id, name, last address, certificate,
aliases, originals archive). Reset and Import keep them; Export leaves
them out.
- SyncHost records each server the first time it signs in with an id. It
names the cache and workspace folders by that id, and re-keys the
folders a server had under its addresses at sign-in. The re-key waits
while transfer or workspace jobs are pending.
- Download originals goes to the server's own archive. It is created
beside this PC's archive at the first download, and a toast says
where. A sequence that already has a local copy keeps receiving into
that copy's archive. A server without an id keeps the 1.0 behaviour.
- At start, after the index opens and before any job runs, the folders
are sorted into their homes. A toast reports the result: sorted,
pending or failed.
- The workspace host gives each home's store its own sync. Find, List,
usage, clean-up and the trash plan and empty cover every home. Server
comparisons go through the identity, so a project stays Online when
its server is reached by another address.
- The render-node downloads and the server import staging move into the
server's folder of the cache. The cache trim keeps `servers`, and the
scheduled scan also scans the originals archives.
- Settings shows the Home folders rows (Workspace) and the Known servers
table (Server). The diagnostics bundle lists the homes.
- The dead `AppPaths.CreateDirectories` and `ThumbnailsDirectory` are
removed.
Refs #66
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Chronos Server for Windows is replaced by Settings > Server > Share this
library: Chronos Desktop hosts the server engine in its own process over its
own index, archive and processing services, job engine and scheduler, so a
second PC, the Uploader and render nodes use this PC's library without a
Windows service or a second index.
- Chronos.Server is a library; Chronos.Server.Host is the console exe that
Docker and development runs start. The App references the library and the
ASP.NET Core shared framework (no package).
- ServerHost.BuildHosted/HostedServer: reuses the desktop's engines and
never creates, starts or disposes them; no static log sink, no console
lifetime; server.json plus desktop-owned values locked "Set in Chronos
Desktop"; only upload-cleanup and audit-cleanup schedules are added.
- Both modes: by-id endpoints scoped to the served archive, a client's
render export folder dropped; hosted mode exposes server job kinds only.
- Desktop: LibraryShare (start after the schedules, stop first, port in
use named), Settings > Server sharing rows, Server > This library panel
(state, addresses with Copy, ports, fingerprint, temporary admin
password, clients, admin panel), own library refused by ConnectFlow and
dropped from LAN discovery, the uploads sweep step, thumbnails after scans
while sharing, capture scenes server-share and server-share-failed.
- Removed: the Windows service hosting of Chronos.Server, its switches and
its tests.
Refs #67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The six parcels of owner review 5 merged into or5-v1.1 need a few joins
that no single parcel owned:
- The workspace copy and send jobs compare a project's home server
through WorkspaceJobOptions.SameServer, so a job queued under a
server's 1.0 address still runs once its home is re-keyed to the
server id (plan step S3), with a test against a real server.
- The sample data gives its running and paused jobs a progress detail
(SampleJobDetails), so the captures show the status line.
- The Windows service strings (Server.Service.*) went with the service
hosting; they are removed line by line from all 38 cultures.
- The VS Code launch and build task start Chronos.Server.Host, now that
Chronos.Server is a library.
Docs: CHANGELOG [Unreleased], DECISIONS rows, BRIEF amendments and the
section 24 rows for R1-R4, ARCHITECTURE, the deploy guides (Chronos
Server in Docker only; on Windows Chronos Desktop shares its library),
both READMEs and STATUS (owner review 5 in progress for v1.1.0).
Refs #64#65#66#67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Setup: a kept 1.0 Uploader no longer fixes the scope and folder, the
Remove tooltip promises kept files only with a hashed log, and a
single-program setup preselects it. The Uploader always downloads the
setup. Sync links move to the server id at every sign-in while folders
wait for jobs and open editors; jobs of a pending homes sort still find
their projects. A shared library exposes only the shared archive's
client-visible jobs and events, render nodes take only client renders,
and the share counts as its own while starting. Progress: a new step
waits a quarter interval and a trailing timer publishes the last state;
the job bar tooltip carries the whole line; Recent maintenance and the
Server jobs list pick up jobs that start while they are shown.
Refs #64#65#66#67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The owner wants the shared library to keep running while Chronos runs.
While sharing is on (or on its way), closing the main window now hides it
behind a tray icon (Open Chronos, Exit) instead of ending Chronos. Exit asks
first when clients used the library in the last minutes, then closes the
window for real, so the editor still stores its last edit and the exit path
stops sharing before the other services. A start at sign-in (--minimized)
with sharing on waits in the tray. With sharing off nothing changes.
The decisions live in ShareLifetime (unit-tested); ShellTray wires them to
the window, LibraryShare and OsNotifications, whose balloons reuse the icon.
Server > This library also warns when the 1.0 Windows Server's service
(ChronosServer) is installed, through a read-only SCM P/Invoke probe.
Refs #67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The job bar and lists show the progress detail; new setup (update,
retained 1.0), Server jobs and Share scenes.
Refs #64#65#66#67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Translates the new and changed strings into the 36 other languages,
sets the default version to 1.1.0 and closes the request, STATUS and
CHANGELOG for the release.
Refs #64#65#66#67
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Alby96
merged commit 20d64af4a4 into main2026-11-15 18:12:03 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Owner review 5 (2026-11-15), released as
v1.1.0. Request, answers and plan:docs/requests/2026-11-15-owner-review-5.md.Chronos-Setupinstalls and updates Chronos Desktop and/or Chronos Uploader. Chronos Server is Docker only. A 1.0 Windows Server install is shown as "no longer offered" and can be removed, as a planned, explicit action. The Uploader checks for updates and downloads the single setup. The update code is shared inChronos.Core/UpdatesandChronos.Ui/Updates.servers\<id>, apart fromlocal. The 1.0 workspace and cache are sorted into this layout at the first start. Sync links are re-keyed to the server id.Chronos.Serverbecomes a library, andChronos.Server.Hostis the Docker exe. Shared mode exposes only client jobs on the shared archive. While sharing, closing the window hides Chronos to the tray. The desktop warns when the 1.0 Windows service is still installed. The Windows service hosting is removed.Checks on the PC:
Not run on the PC: the Windows-only smoke tests,
installer-test.ps1and the release dry run.Follow-ups (not in this PR):
Closes #64
Closes #65
Closes #66
Closes #67
🤖 Generated with Claude Code
The desktop keyed every server by the address it was reached at, so one NAS reached by name and by IP, or after an address change, looked like two servers, and all servers shared one workspace and one cache. Each server now announces a stable id, and the desktop's folders are sorted into one home per server, so that every server can have its own archive of downloaded originals (or5 answers Q1). - The server makes a Guid v7 once, keeps it as the app setting server.id (so it survives restarts and restores, on SQLite and Postgres) and announces it as ServerInfo.ServerId. Older clients ignore the field, and older servers read as null. - ServerIdentity keys a server as id:<N> when it announces an id, and by its address otherwise. Address keys are kept as aliases. - HomeFolders names the homes: local, servers/<id> or servers/addr-<hash16>. The hash equals the 1.0 proxy cache folder name. It also names the per-server originals archive root. - WorkspaceHomes splits the workspace into one format-1 store per home under a format-2 parent manifest, which 1.0 refuses. A 1.0 workspace stays one store until it is sorted. - HomeLayoutMigration plans as a dry run and applies through a journal: - only same-folder renames, each checked by inventory; - a clash keeps the copy saved last and sends the other to the trash; - it resumes after a crash at any step; - it skips leased projects; - it defers an offline workspace or one being moved, while the cache part still runs. - RekeyAsync moves an alias home to the id home: whole folders, or project-by-project merges. It also rewrites working states under their lease, and moves sync_links (the newer row wins a clash). - ProxyCache, the job root resolver, WorkspaceMover and WorkspaceCleaner understand the split layout. The new layout is opt-in through SyncOptions.ServersDirectory, so the app sees no change until it is wired. Refs #66 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>