Files
Chronos/src/Chronos.App/Editor/ExportSync.cs
T
Alby96andClaude Opus 5.5 f2b58522b9
CI / Build and test (push) Successful in 8m14s
CI / Windows tests and installer (push) Skipped
CI / YAML check (push) Successful in 7s
Release / Build, test and publish (push) Successful in 13m19s
CI / PostgreSQL 16 integration (push) Successful in 4m49s
CI / PostgreSQL 17 integration (push) Successful in 5m28s
CI / Docker image (push) Successful in 53s
Release / Server image (push) Failing after 10s
refactor!: rename Titano to Chronos and move CI and releases to Gitea (#6)
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>
2026-10-23 12:45:18 +02:00

80 lines
3.7 KiB
C#

using System.IO;
using Chronos.Core.Model;
using Chronos.Data;
using Chronos.Data.Jobs;
using Chronos.Data.Processing;
using Chronos.Data.Sync;
namespace Chronos.App.Editor;
/// <summary>Whether the Export "Sync" option can be used, or why not (its tooltip says which).</summary>
public enum ExportSyncGate
{
Available,
/// <summary>A server sequence: its renders are made on the server and stay there.</summary>
Remote,
/// <summary>No server session is open.</summary>
SignedOut,
/// <summary>The server does not have this sequence.</summary>
NotLinked,
/// <summary>The account may not send files to the server.</summary>
NoUpload,
}
/// <summary>What became of the Export "Sync" of a finished render.</summary>
/// <param name="Gate">Why the render was not sent, or <see cref="ExportSyncGate.Available"/>.</param>
/// <param name="Send">The queued send job; null when it was not queued.</param>
public sealed record ExportSyncResult(ExportSyncGate Gate, Job? Send);
/// <summary>
/// Export "Sync" (Export.html "register the export on the server when connected", BRIEF §14.5): a render made on this
/// PC whose export asked for it is sent to the server the sequence is linked to once it is done
/// (<see cref="SyncService.EnqueueSendExportsAsync"/>). The choice travels inside the render job (its export), so it
/// holds after the editor closes; a render that ends while the session is down is queued for the last session's server
/// and its send waits for the session (and fails visibly on the Jobs screen when it does not come back).
/// </summary>
public sealed class ExportSync(ChronosDatabase db, SyncService sync, JobEngine engine)
{
/// <summary>The option's state for a sequence.</summary>
/// <param name="server">Key of the signed-in server; null while signed out.</param>
/// <param name="linked">The server has the sequence (a sync link joins them).</param>
public static ExportSyncGate Gate(bool isRemote, string? server, bool linked, bool canUpload) =>
isRemote ? ExportSyncGate.Remote
: server is null ? ExportSyncGate.SignedOut
: !linked ? ExportSyncGate.NotLinked
: !canUpload ? ExportSyncGate.NoUpload
: ExportSyncGate.Available;
/// <summary>Queues sending a finished render's output.</summary>
/// <param name="server">Key of the server: the signed-in one, else the one of the saved session; null without either.</param>
/// <param name="canUpload">The account may send files (assumed while the session is down: the server refuses the send otherwise).</param>
/// <returns>The send job or why there is none; null when the job is not a finished render of this PC that asked for it.</returns>
public async Task<ExportSyncResult?> SendAsync(Job job, string? server, bool canUpload, CancellationToken cancellationToken = default)
{
ArgumentNullException.ThrowIfNull(job);
if (job is not { Kind: JobKind.Render, State: JobState.Done, TargetIds: [var target] } || !Wanted(job)) return null;
if (await db.Sequences.GetAsync(target, cancellationToken) is not { } local) return null;
var linked = server is not null && await sync.LinkOfAsync(server, local.Id, cancellationToken) is not null;
var gate = Gate(false, server, linked, canUpload);
return gate == ExportSyncGate.Available
? new ExportSyncResult(gate, await sync.EnqueueSendExportsAsync(engine, server!, local, cancellationToken))
: new ExportSyncResult(gate, null);
}
private static bool Wanted(Job job)
{
try
{
return ProcessingJobs.ReadRender(job.ParametersJson).Export.SyncToServer;
}
catch (InvalidDataException)
{
return false;
}
}
}