Skip to content

v1.2.0

Choose a tag to compare

@msx752 msx752 released this 01 Nov 13:37
· 322 commits to main since this release
f045870
dotnet add package SharpTicker --version 1.2.0

All SharpTicker.* packages share one version and are released together: update them together to 1.2.0.

Changes you may notice

These apply when you upgrade from 1.1.0. There is no database change.

Area In 1.1.0 Now What to do
Priority of [TickerFunction] High, Normal and Low were accepted and ignored When more jobs are ready than there are workers, High starts before Normal and Normal before Low, first in first out within one priority. After ten High or Normal jobs in a row, a waiting Low job goes next. LongRunning still bypasses the pool Only if you set High or Low and have more ready jobs than MaxConcurrency: the order in which jobs start changes.
Status of a chain in the Time Tickers list Done when its first job was Done Shown as PartiallyDone (amber) when a job below it failed or was cancelled. A skipped job does not count: a child that runs only on failure is skipped by design Nothing. It is a label otatus is still Done.
Executed At column How long ago The exact time (the time ago is on hover), with the duration in its own column.
A running job shows moving dots, a skipped j
Words in the dashboard Job, ticker and function used for the same thing One vocabulary: function is the registered code, ticker is the scheduled entry, job is one run Nothing.
Restart and Stop System Two buttons One System menu, each action asks for confirmation Nothing.
Dashboard statistics All-time and past-7-days counts mixed, success rate always 100% One scope per number and an honest success rate Nothing.

Added

  • Dashboard visibility rule (`WithVisibile decides which time tickers, cron tickersand functions a signed-in user may see. It applies to lists, pages, charts and counts, to every read and action on a single ticker (a hidden ticker answers as if it did not exist), to adds and updates (a function the user may not use is refused), and to live notifications. The scheduler controls are not tied to the rule on purpose: protect them with
    the dashboard's own authentication. Without he dashboard guide.
    inds nothing to cancel.

Fixed

  • A live update never reached the dashboard in an application with reflection-based serialization turned off.
  • The Time Tickers and Cron Tickers pages loaded twice on a first open and stalled while they opened. The requests now
    start together, the charts are drawn after t elements per row.
  • A time ticker deleted in the dashboard stayed on screen on other open dashboards.
  • A skipped job showed an Executed At time ah it never ran.
  • Batch update of tickers on EF Core with net8.

Security

While adding the visibility rule, reviews found several places where a user could get at tickers of another team, and
each was closed with a test. Only applicatio rule are affected, and the rule is new inthis release.

Known issue

Rows left InProgress by a process that ends without a signal (SIGKILL, out of memory, node loss) are not released with the EF Core store when the replacement er`. Use a stable identifier for now (forexample a StatefulSet pod name); see #24.

Please report problems in Issues.

Full Changelog: v1.1.0...v1.2.0