Skip to content

1.0.0-rc.9

Pre-release
Pre-release

Choose a tag to compare

@marko444 marko444 released this 08 Nov 23:36
· 369 commits to main since this release

The ninth release candidate for 1.0.0. It makes deploys explicit, moves the dashboard into its own package, gives operations and the HTTP contract one naming convention, and runs on SQL Server with READ_COMMITTED_SNAPSHOT off as well as on.

Upgrading from rc.8: drop and reprovision every database an rc.8 build provisioned: the baseline is re-cut, and nothing translates it. A worker start no longer writes definitions or schedules: run <app> jobs migrate (schema, then jobs) or <app> jobs deploy (jobs alone) once per release, before the new workers start; in development, MigrateOnStartup = true makes startup do both. The dashboard is the package Acta.Dashboard, so an app that calls MapActa adds it and using Acta.Dashboard;. Operations, responses, routes, and CLI JSON follow one naming convention, so regenerate an OpenAPI client. The release notes list every change a consumer makes.

Highlights

  • <app> jobs deploy writes a release's definitions and schedules in one transaction and records its version; <app> jobs migrate applies the migrations from a deploy step, and each provider's Migrations.ApplyAsync does it from code.
  • A schedule can be finite, bounded to the occurrences between a start and an end, and a per-occurrence definition may declare a deadline.
  • ActaEndpointOptions.RequirePermissions authorizes every request against the host's policy for the operation's permission, GET /capabilities answers the caller's permissions, and the dashboard shows only the controls the caller holds and stops on an ended session.
  • The OpenAPI document describes every property, schema, path parameter, and response, with one example request and answer per JSON body taken from the contract tests' host.
  • A handler DI cannot build fails on its first attempt with HandlerActivationException instead of retrying for days, a cancelled job's explanation gives the cancel's reason, and a job that failed for good resolves its retrying alerts.
  • SQL Server runs and is tested with READ_COMMITTED_SNAPSHOT on and off, and Acta switches it on only in a database its development flag has just created.

Evidence: the engine is certified on 096ea16e5; the commits after it change the site and how Acta Verify frames the site's benchmark page, so the certified commit is 7c4dae04c. Under the Acta Verify release suite on PostgreSQL, SQL Server, and SQLite, every correctness, fault, and chaos scenario passed and every trial's ledger passed the certification checks. Every performance floor held but one: sixteen SQL Server workers at 4,000/s missed in the run (p99 2.2 s against 2.0 s) and in the first of four reruns, then held in the three after it, each completing about 4,000 jobs a second; the known limitations name the short enqueue stalls behind it. The chaos certification ran 1,000,000 jobs on PostgreSQL and on SQL Server with a worker killed every 5 s, and every busy worker's work was reclaimed. Four PostgreSQL workers completed 12,527 fully executed, durably completed jobs per second with p99 1.0 s, one worker woken in process 7,500 with p99 49 ms, and eight workers drained a backlog of a million jobs at 73,864 a second. Report: docs/reference/benchmark.md and useacta.net/benchmark.

Release notes: https://github.com/acta-dotnet/acta/blob/v1.0.0-rc.9/docs/release-notes.md