CI / Build and test (pull_request) Failing after 2m3s
CI / PostgreSQL 16 integration (pull_request) Skipped
CI / PostgreSQL 17 integration (pull_request) Skipped
CI / Docker image (pull_request) Skipped
CI / Windows tests and installer (pull_request) Skipped
CI / YAML check (pull_request) Successful in 4s
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. 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) and pe-check. 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>
48 lines
1.8 KiB
C#
48 lines
1.8 KiB
C#
using System.Windows;
|
|
using System.Windows.Threading;
|
|
using Chronos.Ui.Theming;
|
|
|
|
namespace Chronos.App.Tests.Windows;
|
|
|
|
/// <summary>
|
|
/// The process-wide WPF <see cref="Application"/> (only one may ever exist per process) on its own STA thread with
|
|
/// the Chronos theme. Every WPF test reaches it through here, whichever test happens to run first.
|
|
/// </summary>
|
|
internal static class WpfApplication
|
|
{
|
|
private static readonly Lazy<(Dispatcher Dispatcher, Thread Thread)> Instance = new(Start, LazyThreadSafetyMode.ExecutionAndPublication);
|
|
|
|
public static Dispatcher Dispatcher => Instance.Value.Dispatcher;
|
|
|
|
/// <summary>
|
|
/// Stops the dispatcher in order (its binding engine and windows clean up on their own thread) and waits for it, so the
|
|
/// process exits without WPF work racing its teardown. Nothing to do when no WPF test ran.
|
|
/// </summary>
|
|
public static void Shutdown()
|
|
{
|
|
if (!Instance.IsValueCreated) return;
|
|
var (dispatcher, thread) = Instance.Value;
|
|
if (!dispatcher.HasShutdownStarted) dispatcher.InvokeShutdown();
|
|
thread.Join(TimeSpan.FromSeconds(10));
|
|
}
|
|
|
|
private static (Dispatcher, Thread) Start()
|
|
{
|
|
Dispatcher? dispatcher = null;
|
|
using var ready = new ManualResetEventSlim();
|
|
var thread = new Thread(() =>
|
|
{
|
|
var app = new Application { ShutdownMode = ShutdownMode.OnExplicitShutdown };
|
|
ThemeManager.Initialize(app, AppTheme.Dark);
|
|
dispatcher = System.Windows.Threading.Dispatcher.CurrentDispatcher;
|
|
ready.Set();
|
|
System.Windows.Threading.Dispatcher.Run();
|
|
});
|
|
thread.SetApartmentState(ApartmentState.STA);
|
|
thread.IsBackground = true;
|
|
thread.Start();
|
|
ready.Wait();
|
|
return (dispatcher!, thread);
|
|
}
|
|
}
|