The internal fact store gained variable binding, count-threshold triggers and budget waiting.
What's wrong with this entry?
The internal world store, a fact and subscription engine not exposed to users, was substantially extended. Patterns can bind variables, subscriptions can fire on a count threshold, and work can be charged against budgets and made to wait for headroom.
- Patterns bind with
v("x"); the parse error now reads that a pattern must be a JSON object, nested objects as subsets, arrays exact. - A subscription can use an
$atleastform that fires once per binding group when enough matching rows exist. - Storing a budget fact requires a finite, non-negative numeric
units. - Evaluation now has an admission step that waits for budget headroom and rejects with
retracted while waiting for budgetif cancelled first; spend is charged up the scope chain. - Pending work is tracked in an explicit in-flight set so admitted-but-not-started work is not double counted.
a {topic:'budget'} fact needs a finite, non-negative numeric units``
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.239
Workflow tool gains run operations, with the auto-approval hook switched off
Both mention workflow
-
v2.1.239
Workflow tool has a second command shape built in but switched off
Both mention workflow
-
v2.1.239
Workflow "v2 run" handles are scaffolded but never created
Both mention workflow