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 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>