Repository navigation
1.0.0-rc.10
Pre-releaseThe tenth release candidate for 1.0.0. It widens the job counters to 64 bits, removes the columns and codes that carried no information, makes a schedule any distance behind decidable, records operator actions at every level, and gives typed result reads a form that returns the result and a form that says whether one exists.
Upgrading from rc.9: drop and reprovision every database an rc.9 build provisioned: the baseline is re-cut, and nothing translates it. The release notes list each change a consumer must make, with the old and the new spelling.
Highlights
- An execution number and a version are 64-bit, in the tables, the API and the HTTP contract, so a long-lived permanent job no longer has a counter to wear out.
- A schedule that fell years behind is decided by a bounded search, and a schedule a build cannot read is left alone instead of stopping its namespace's admission.
- A suspended job wakes only for the signal or child it waits on, and a child that lands after its parent finished still records its outcome there.
- Pause, resume, restart, reschedule, a priority change, an input update and a caller's cancel are recorded at every recording level, and who did it is in
events.actor. - Retention walks one namespace's jobs at a time and deletes in its first pass; a job with an undelivered alert is kept until the alert settles.
GetResultAsync<T>returns the stored result and throws when there is none;TryGetResultAsync<T>answers(Found, Value). A handler starts a child by its generated call, andGetHandleAsync<T>rebuilds a typed handle from a ref.- A calendar definition has a published JSON Schema and a stated promise for 1.x.
- One alert channel that does not answer no longer holds up the others.
Evidence: the Acta Verify release suite passed on PostgreSQL, SQL Server, and SQLite in one run with no rerun: every correctness, fault, and chaos scenario, every trial's ledger checks, and every performance floor. Chaos ran 1,000,000 jobs on PostgreSQL and on SQL Server with a worker killed every 5 s. Four PostgreSQL workers completed 14,857 fully executed, durably completed jobs per second, held through three 30 s passes and a 120 s confirmation at 15,000/s offered with p99 1.6 s; SQL Server held 5,000 a second. The run's commit was d20e7c77e; its commit messages were reworded afterwards with no change to any file, and the commits after it change documentation, the site, two queries of one lab, test code (the connection timeout of the conformance suites' hosts, one skipped case, and two waits that no longer depend on the runner's speed), and the CI workflow. The report is docs/reference/benchmark.md.
Known limitation: on zone data that gives a zone negative daylight time, which is Europe/Dublin on Ubuntu 26.04, a cron in that zone stops at the spring clock change and skips the repeated hour in autumn, because .NET 10 misreports the zone's skipped and repeated hours (dotnet/runtime#120915). Declare such a schedule in Europe/London, which keeps the same clock.
Release notes: https://github.com/acta-dotnet/acta/blob/v1.0.0-rc.10/docs/release-notes.md