Repository navigation
Schedule, limit, chain and watch jobs, released as 0.7.0 - #2
Merged
Merged
Conversation
What a business system asks of a queue after the core -- periodic jobs, limits across runners, pausing in an incident, runners known to each other, jobs that wait for others, and somewhere to watch it all -- spool did not do, and an application wrote its own or went without. A queue's pause and limits live in its row, where every runner reads them, and a limited queue is claimed under its lock, so two runners cannot each half-obey a limit; partitions are taken in turns. A schedule's tick is enqueued by the compare-and-set that moves it, so it is one job with no leader. A workflow is the jobs connected by waiting, with no object of its own. The dashboard is routes of the application's own Spindle server, deciding who may do what by the application's own users through Spindle's Access, and writing only through spool's functions; its page is built and committed, so it installs with OCaml alone. The guides gain a page on spool in a Spindle application. AGENTS.md keeps only what is spool's own, and make lint runs litany, so the rules a search held are held on every change; the page's generated JSX is kept from the one rule its preprocessor trips. The stages were to be released one by one; they ship together, since the dashboard and the features it shows were tried as one.
CI installed solidtype 0.11.1, whose page code differs from 0.11.0's, so its rebuild of the committed bundle differed; the bundle is now built on it, and the ranges start there. 0.11.1 marks the props check around each tag as generated, so litany no longer needs keeping from the page.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
What a business system asks of a queue after the core -- periodic jobs, limits across runners, pausing in an incident, runners known to each other, jobs that wait for others, and somewhere to watch it all -- spool did not do, and an application wrote its own or went without.
Changes
Spool.statehasBlocked, for a job that waits for others; spool's new migrations must run before a runner of this version starts (rowtype-migrate up --source spool).Spool.Queue.pause,resumeandset_limits, limits across every runner, by rate, and per partition, partitions taken in turns.Spool.Schedule.make, a cron expression read in a named time zone, one job a tick however many runners hold it.Spool.enqueue_after ~waits_for, run once every job it waits for completed, cancelled once one ends otherwise;Spool.workflow.~unique_for,Spool.enqueue_many,Spool.jobs,Spool.delete,Spool.run_again,Spool.Runner.list,Spool.Stats.since, sensitive kinds.spool-dashboard: routes of the application's own Spindle server, who may do what decided by the application's own users through Spindle'sAccess, its page built in.make lintruns litany; AGENTS.md keeps only what is spool's own.Verified
make lint, litany among it, andmake test: 77 tests, against a real Postgres.make docs: the site built, its link check passing.