A whole folder imported again to the server sent its folder name as the
sequence title on every run, undoing a rename made on the server. The
sink now sends a typed title as before, but the folder's default name
only to a sequence that has no title yet (it reads the sequence first).
The archive already applied a title only when it created the sequence.
A session that ends on another day, as a whole folder often does,
showed only its first date ("28/09/2026 · 18:02 → 18:05"), which read
as a few minutes on one day. Its plan row and Show plan heading now
show both dates, from two new invariant resources (with the
right-to-left arrow).
The Gap and Minimum boxes now show their tooltip while disabled, so the
reason Whole folder turns them off reaches them, not only the Sessions
check box. Doc comments that said a merge needs the same camera now
mention the whole-folder rule.
Tests: a server whole-folder import run twice keeps the server's rename
and still applies a typed title; multi-day time text in both reading
directions; and the Import view model's Group rules (folder only, cards
planned by sessions, switching drops splits, tooltips say why).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The release step decided :latest and the releases repository's content
after the Gitea release was already public, and could then fail or decide
wrongly (owner review 2, phase 1 review):
- Re-publishing v0.1.0-rc.1 or rc.2 builds Chronos.Tools from the tag,
which has no release-channels: the step failed after publishing and the
image job never ran. Any failure to decide (a tag older than the
command, an unreadable page, a body that is not a list) now warns and
moves no channel, so the version's image is still pushed.
- Only the first page (50, newest first) of releases was read, and
pre-releases now share it with stable ones: 50 pre-releases after a
stable release hid it and moved :latest to a pre-release. The workflow
reads every page up to the first empty one (at most 100) and
release-channels takes one --releases file per page (Args.GetAll).
- The Version step accepted tags release-channels refuses (v01.2.0), which
then failed only after publishing. It now uses release-channels' SemVer
2.0 pattern without +BUILD, and a test keeps the two in step.
BRIEF §19.3, DECISIONS, CHANGELOG and README step 5 say so.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The Unraid share tooltip told users only to map the share's array view to
/space. With CHRONOS_SPACE_PATH unset (the shipped docker-compose file, or a
template whose Space path was cleared) the server never looks at /space, so
following the tip changed nothing. The tip (en, it) and BRIEF 14.8 now also
say to set CHRONOS_SPACE_PATH=/space; the English text was shortened to stay
within the 200-character tooltip budget.
A render node completing its result on a full archive volume answers 507
before the upload moves to Committing, but no test covered that path. The new
VolumeSpaceTests case checks that the upload keeps receiving with its chunks
and the node keeps the job, then that the same call succeeds once there is
room.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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>