task-serializer
v2.1.4
Published
Serialize tasks/promises for integrated control. Option for limiting number of concurrent tasks.
Downloads
6
Maintainers
Readme
copyright 2020 craigphicks ISC license
TaskSerializer
Outline
The TaskSerializer
module can serialize tasks/promises for integrated control - Tasks/promises can be added immediately as they are produced and then be made available to a consumer when they have resolved and the consumer is ready to read them.
Optionally, the number of concurrently running tasks are limited to a user parameter. In that special case, only functions (and their args) may be added, and function will be executed when a space is available. Trying to add promises will throw an Error.
The are 4 different classes exported from the module:
AsyncIter
NextSymbol
WaitAll
Callbacks
See Essential Information for a discussion of their behavior and differences.
The module is not dependent upon NodeJS, so can be used in browser code.
Usage examples
Note on shared demo functions
To make the examples more readable some shared function are used. They are listed at the end of these examples.
One of those shared functions is the async function producer()
. It inputs the tasks by calling install.addTask(...)
staggered over time, followed by install.addEnd()
. Some of those tasks throw Errors
, other resolve normally.
Typescript
Typescript .d.tds
files are bundled with the modules. Section Typescript usage examples lists typescript versions of the javascript examples below.
Automatic creation of examples
Both the JS and TS version of the examples can be create by calling
source node_modules/task-serializer/scripts/post-install-demo.sh
from the npm project directory from which npm install task-serializer
was called. Two directories demo-js
and demo-ts
are created, and all the examples are run.
The ts
setup has some side effects (e.g., install typescript
locally), and to avoid that
source node_modules/task-serializer/scripts/post-install-demo-jsonly.sh
should be called instead.
AsyncIter
usage example
'use strict';
const {AsyncIter}=require('task-serializer');
const {producer}=require('./demo-lib.js');
async function consumer(ai){
do{
try{
for await(const res of ai){
console.log(' '+JSON.stringify(res));
}
break;
}catch(e){
console.log(' '+'error: '+e.message);
}
}while(true);
}
async function main(){
let ai=new AsyncIter({concurrentTaskLimit:2});
await Promise.all([producer(ai),consumer(ai)]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
NextSymbol
usage example
'use strict';
const {NextSymbol}=require('task-serializer');
const {makepr,producer}=require('./demo-lib.js');
var somethingElse=makepr();
var iv=setInterval(()=>{somethingElse.resolve("somethingElse");},300);
async function consumer(ts){
let emptied=false;
while(!emptied){
let next = await Promise.race([
somethingElse.promise,
ts.nextSymbol(),
]);
switch(next){
case "somethingElse":
console.log(next);
somethingElse=makepr();// reset
break;
case ts.symbolTaskResolved():{
console.log();
let res=ts.getTaskResolvedValue();
console.log("symbolTaskResolved, result="+res);
break;}
case ts.symbolTaskRejected():{
let e=ts.getTaskRejectedValue();
console.log("symbolTaskRejected, message="+e.message);
break;}
case ts.symbolAllRead():{
console.log("symbolAllRead");
emptied=true;
clearInterval(iv);
break;}
}
}
}
async function main(){
let ts=new NextSymbol({concurrentTaskLimit:2});
await Promise.all([consumer(ts),producer(ts)]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure: '+e.message);});
WaitAll
usage examples
'use strict';
const {WaitAll}=require('task-serializer');
const {producer}=require('./demo-lib.js');
async function consumer_waitAll(ts){
try{
let r=await ts.waitAll();
console.log(`ts.waitAll() returned`);
console.log(JSON.stringify(r,0,2));
}catch(e){
console.log(`ts.waitAll() caught ${e.message}`);
}
}
async function consumer_waitAllSettled(ts){
let r=await ts.waitAllSettled();
console.log(`ts.waitAllSettled() returned`);
console.log(JSON.stringify(r,0,2));
console.log('consumer finished');
}
async function main(){
let waitAll=new WaitAll({concurrentTaskLimit:2});
await Promise.all([
consumer_waitAll(waitAll),
producer(waitAll),
]);
waitAll=new WaitAll({concurrentTaskLimit:2});
await Promise.all([
consumer_waitAllSettled(waitAll),
producer(waitAll),
]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
Callbacks
usage example
'use strict';
const {Callbacks}=require('task-serializer');
const {producer}=require('./demo-lib.js');
async function consumer(ts){
await new Promise((resolve)=>{
ts.onTaskResolved((resolvedValue)=>{
console.log(`onTaskResolved ${resolvedValue}`);
});
ts.onTaskRejected((rejectedValue)=>{
console.log(`onTaskRejected ${rejectedValue}`);
});
ts.onEmpty(()=>{
console.log(`onEmpty`);
resolve();
});
});
console.log('consumer finished');
}
async function main(){
let ts=new Callbacks({concurrentTaskLimit:2});
await Promise.all([
consumer(ts),// consumer must initialize first
producer(ts)
]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
demo-lib.js
'use strict';
var {AsyncIter,NextSymbol}=require('task-serializer');
function snooze(ms){return new Promise(r=>setTimeout(r,ms));}
function range(len){return [...Array(len).keys()];}
function makepr(){
let pr={};
pr.promise=new Promise((r)=>{pr.resolve=r;});
return pr;
}
function logStatus(ts){
let wa=ts.getCountWaiting();
let wo=ts.getCountWorking();
let rest=ts.getCountResolvedTotal();
let rejt=ts.getCountRejectedTotal();
let fint=ts.getCountFinishedTotal();
console.log(
`wa:${wa},wo:${wo},rest:${rest},rejt:${rejt},fint:${fint}`);
if ((ts instanceof AsyncIter)||(ts instanceof NextSymbol)){
let resnr=ts.getCountResolvedNotRead();
let rejnr=ts.getCountRejectedNotRead();
console.log(`resnr:${resnr},rejnr:${rejnr}`);
}
}
async function task(id,ms,err=false){
console.log(`-->enter ${id}`);
if (err)
throw new Error(`task failed id=${id}`);
await snooze(ms);
console.log(`<--leave ${id}`);
return `task ${id}, took ${ms}ms`;
}
async function producer(ts){
for (let i=0; i<6; i++){
ts.addTask(task,i,2**(10-i),(i+1)%3==0);
await snooze(100);
}
ts.addEnd();
console.log('producer finished');
}
module.exports.snooze=snooze;
module.exports.task=task;
module.exports.range=range;
module.exports.makepr=makepr;
module.exports.producer=producer;
Esential Information
Classes share common input functions
Each of the classes includes these input functions:
addTask(func,...args)
/addTask(promise)
to add tasks/promises.addEnd()
to indicate that no more tasks/promises will be added, thus allowing exit after the pipeline has drained.
Classes have differing output functions and behavior
The output interface of each of those classes differ, and are suitable for different usage cases. The following table compares some properties of those classes to help decide which is suitable for a given usage case:
| property |AsyncIter
|NextSymbol
|WaitAll
|Callbacks
|
|-- |-- |-- |-- |-- |
| read buffered | yes | yes | yes | no |
| continuous vs. batch |cont | cont | batch | cont |
| control loop | yes | yes | no | no |
| select style | no | yes | N/A | N/A |
||||||
where 'property' are as follows:
- 'read buffered':
- Whether the class has an internal buffer storing the outcomes of finished tasks/promises until they are read by the consumer.
- 'continuous vs. batch':
- Batch indicates either:
- no consumer read until all tasks/promises have resolved, or until any tak/poromise has rejected (
WaitAll.waitAll
) - no consumer read until all tasks/promises have either resolved or rejected (
WaitAll.waitAllSettled
)
- no consumer read until all tasks/promises have resolved, or until any tak/poromise has rejected (
- Continous indicates the internal read buffer is intended to be read by consumers before all taks/promises have resolved/rejected.
- Batch indicates either:
- 'control loop'
- The output may be easily read in an asynchrous control loop
- 'select style'
- The control loop condition informs an output is 'ready' without actually reading it. This style is useful for a top level control loop integrating 'ready' conditions from many unrelated sources. (See
NextSymbol
usage example.)
- The control loop condition informs an output is 'ready' without actually reading it. This style is useful for a top level control loop integrating 'ready' conditions from many unrelated sources. (See
Resolve/Reject handling
All rejected tasks/promises are managed so that they don't throw unhandled rejections.
Read-buffered classes prioritize rejected-values over resolved-values, and pass the rejected-values first whenever both are availabe. The exception to this rule is WaitAll.waitAllSettled()
, which transforms rejected-values into resolved-values.
Terminology
Each task/promise after being added will go through all of the following milestones in order:
- added
- The task has been added with
addTask
.
- The task has been added with
- started
- If the construtor parameter
concurrentTaskLimit
>0, then a task may be forced to wait before start. - If the construtor parameter
concurrentTaskLimit
<=0, that all task/promises are (considered) started when added.
- If the construtor parameter
- finished
- Task/promise has reached an outcome, either one of the following two categories:
- resolved-value
- resulting from
resolve(<resolved-value>)
orreturn <resolved-value>
- resulting from
- rejected-value
- resulting from ``reject()
or
throw ` - The actual values are determined by the task/promise, not by the
TaskSerializer
module. A rejected-value typically satisfies(<rejected-value> instanceof Error)
, but that is not mandatory.
- resulting from ``reject()
- resolved-value
- Task/promise has reached an outcome, either one of the following two categories:
- read
- This milestone is seperate from finished only in the read-buffered classes
AsyncIter
,NextSymbol
, andWaitAll
. In the case of classCallbacks
, one of theonTaskResolved
/onTaskRejected
callbacks is called immediately when finished is reached, so read and finished are reached simultaneously. - Task/promise outcome has been read by the consumer.
- This milestone is seperate from finished only in the read-buffered classes
- added
The class instance passes through the following milestones, in order:
- started-processing
- First task/promise has been added.
- ended
addEnd
has been called to guarantee no more tasks/promises will be added.
- all-finished
addEnd
has been called and all added tasks/promises have reached finished.
- all-read
- This milestone is seperate from all-finished only for the read-buffered classes
AsyncIter
,NextSymbol
, andWaitAll
. In the case ofCallbacks
, one of the callbacksonResolved
/onRejected
will be called immediately upon reaching finished.
- This milestone is seperate from all-finished only for the read-buffered classes
- started-processing
Termination
There is no active termination method. The TaskSerializer class instances always wait for added tasks to reach finished. Therefore, if the task deadlocks or runs forever, the class instance does not terminate.
APIs
API shared by all classes
instance=new <Classname>({concurrentTaskLimit=0}={})
- where
<Classname>
is one ofAsyncIter
,Callbacks
,NextSymbol
,orWaitAll
. concurrentTaskLimit
is the integer number of task allowed to run concurrently, unless it is<=0
, in which case their is no limit.
- where
instance.addTask(func,...args)
where(func instanceof Function)
, oraddTask(promise)
where(promise instanceof Promise)
- in the case of constructor arg
concurrentTaskLimit>0
,addTask
will allow only the first form, and passing a promise will throw.func(...args)
will be called in the order passed, when the concurrent task limit constraint allows.
- in the case of constructor arg
concurrentTaskLimit<=0
, either form is allowed. - in either case, the tasks/promises are managed by the instance of
<Classname>
until reaching miletone read. The tasks/promises may reject, and those rejections are handled to prevent unhandled promise rejections.
- in the case of constructor arg
instance.addEnd()
- this a guarantee from the caller that
addTask
will not be called again. It is required so the instance knows that when all tasks/promises have reached the finished milestone, the instance has reached the finished-processing milestone.
- this a guarantee from the caller that
The following are informational functions common to all the classes.
instance.getCountWaiting()
- When the construct arg
concurrentTaskLimit<=0
, always returns0
. - Otherwise, returns the number of tasks added but not yet started.
- When the construct arg
instance.getCountWorking()
- Returns the number of tasks/promises started but not yet finished.
instance.getCountResolvedTotal()
- Returns the number of tasks/promises finished with a resolved-value
instance.getCountRejectedTotal()
- Returns the number of tasks/promises finished with a rejected-value
instance.getCountFinishedTotal()
- Returns the sum of
instance.getCountResolvedTotal()
andinstance.getCountRejectedTotal()
- Returns the sum of
The following are informational functions available only in the read-buffered classes AsyncIter
and NextSymbol
:
instance.getCountResolvedNotRead()
- Returns the number of tasks/promises finished with a resolved-value, but which are not yet read
instance.getCountRejectedNotRead()
- Returns the number of tasks/promises finished with a rejected-value, but which are not yet read
instance.getCountFinishedNotRead()
- Returns the sum of
instance.getCountResolvedNotRead()
andinstance.getCountRejectedNotRead()
- Returns the sum of
AsyncIter
only API
- see
AsyncIter
usage example for example. const {AsyncIter}=require('task-serializer')
AsyncIter.constructor({concurrentTaskLimit=0}={})
AsyncIter.constructor(concurrentTaskLimit=0)
- Either form of constructor (named/unnamed param) are allowed..
- See API shared by all classes.
- explicit async
instance.next()
or implicit asyncfor await (iter of instance)
- There are 3 possible outcome categories: resolved-value, rejected-value, and all-read, where all-read indicates that the instance has reached the all-read milestone.
- case: explicit
- case: resolved-value
- returns
{done:false,value:<resolved-value>}
- returns
- case: rejected-value
- throws
<rejected-value>
- throws
- case: all-read
- returns
{done:true}
- returns
- case: resolved-value
- case: implicit
- case: resolved-value
iter
will be the<resolved-value>
- case: rejected-value
- throws
<rejected-value>
- throws
- case: all-read
- breaks from loop.
- case: resolved-value
NextSymbol
only API
- see
NextSymbol
usage example for example. const {NextSymbol}=require('task-serializer')
NextSymbol.constructor({concurrentTaskLimit=0}={})
NextSymbol.constructor(concurrentTaskLimit=0)
- Either form of constructor (named/unnamed param) are allowed..
- See API shared by all classes.
- async
instance.nextSymbol()
Returns a value strictly equal to one ofinstance.symbolTaskResolved()
,instance.symbolTaskRejected()
, orinstance.symbolAllRead()
.- case
instance.symbolTaskResolved()
: indicates a task/promise resolved-value is ready to be read. - case
instance.symbolTaskRejected()
: indicates a task/promise rejected-value is ready to be read. - case
instance.symbolAllRead()
: indicates the instance milestone all-read has been reached.
- case
instance.getTaskResolvedValue()
- This is a sync function intended to be called immediately after
async instance.nextSymbol()
has returned a value equal toinstance.symbolTaskResolved()
- It returns the next resolved-value of some task/promise.
- This is a sync function intended to be called immediately after
instance.getTaskRejectedValue()
- This is a sync function intended to be called immediately after
async instance.nextSymbol()
has returned a value equal toinstance.symbolTaskRejected()
- It returns the next rejected-value of some task/promise.
- This is a sync function intended to be called immediately after
WaitAll
only API
- see
WaitAll
usage examples for example. const {WaitAll}=require('task-serializer')
WaitAll.constructor({concurrentTaskLimit=0}={})
WaitAll.constructor(concurrentTaskLimit=0)
- Either form of constructor (named/unnamed param) are allowed..
- See API shared by all classes.
- async
instance.waitAll()
- There is no timing constraint on calling
waitAll
, i.e. no requirement to call before after any instance milestone, although obviously milestone empty is not reached untilwaitAll
is called. - If any tasks/promises have terminated with an error before the call to
addTask
, then that first one will be returned immediately whenwaitAll
is called. - If any tasks/promises have terminated with an error after
addTask
is called,waitAll
will immediately return with that error. - Otherise
waitAll
will not return before all the tasks/promises added withaddTask
have terminated, and the array of resolved-values will be the order they were added, not the order they were resolved.
- There is no timing constraint on calling
- async
instance.waitAllSettled()
- There is no timing constraint on calling
waitAllSettled()
. Any time from before the firstaddTask
to after all tasks/promises have terminated (i.e., end-of-processing) is allowed. Measures have been taken to prevent unhandled rejections. waitAllSettled
will return no sooner than end-of-processing. It will return the same value asPromise.waitAllSettled()
would return on an array of all tasks/promises added viaaddTask
in the order the were added.
- There is no timing constraint on calling
Callbacks
only API
- see
Callbacks
usage example for example. const {Callbacks}=require('task-serializer')
Callbacks.constructor({concurrentTaskLimit=0}={})
Callbacks.constructor(concurrentTaskLimit=0)
- Either form of constructor (named/unnamed param) are allowed..
- See API shared by all classes.
instance.onTaskResolved(callback)
- add the unique callback to be called every time a task/promise resolved-result is ready
instance.onTaskRejected(callback)
- add the unique callback to be called every time a task/promise rejected-result is ready
instance.onEmpty(callback)
- add the unique callback to be called when the instance reaches the empty milestone.
- NOTES:
- Each
instance.on<*>
function should be called only once per instance. Only one callback per function is actually registered. - Each
instance.on<*>
function must be called before the instance has reached the processing milestone, i.e., before the first call toaddTask
.
- Each
Typescript usage examples
AsyncIter
usage example (typescript)
import {AsyncIter} from 'task-serializer'
import {producer} from './demo-lib';
async function consumer(ai: AsyncIter){
do{
try{
for await(const res of ai){
console.log(' '+JSON.stringify(res));
}
break;
}catch(e){
console.log(' '+'error: '+e.message);
}
}while(true);
}
async function main(){
let ai=new AsyncIter({concurrentTaskLimit:2});
await Promise.all([producer(ai),consumer(ai)]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
NextSymbol
usage example (typescript)
import {NextSymbol} from 'task-serializer';
import {makepr,producer} from './demo-lib.js';
var somethingElse=makepr();
var iv=setInterval(()=>{somethingElse.resolve("somethingElse");},300);
async function consumer(ts: NextSymbol){
let emptied=false;
while(!emptied){
let next = await Promise.race([
somethingElse.promise,
ts.nextSymbol(),
]);
switch(next){
case "somethingElse":
console.log(next);
somethingElse=makepr();// reset
break;
case ts.symbolTaskResolved():{
console.log();
let res=ts.getTaskResolvedValue();
console.log("symbolTaskResolved, result="+res);
break;}
case ts.symbolTaskRejected():{
let e=ts.getTaskRejectedValue();
console.log("symbolTaskRejected, message="+e.message);
break;}
case ts.symbolAllRead():{
console.log("symbolAllRead");
emptied=true;
clearInterval(iv);
break;}
}
}
}
async function main(){
let ts=new NextSymbol({concurrentTaskLimit:2});
await Promise.all([consumer(ts),producer(ts)]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
Callbacks
usage example (typescript)
import {Callbacks} from 'task-serializer';
const {producer} from './demo-lib.js';
async function consumer(ts: Callbacks){
await new Promise<void>((resolve)=>{
ts.onTaskResolved((resolvedValue:any)=>{
console.log(`onTaskResolved ${resolvedValue}`);
});
ts.onTaskRejected((rejectedValue)=>{
console.log(`onTaskRejected ${rejectedValue}`);
});
ts.onEmpty(()=>{
console.log(`onEmpty`);
resolve();
});
});
console.log('consumer finished');
}
async function main(){
let ts=new Callbacks({concurrentTaskLimit:2});
await Promise.all([
consumer(ts),// consumer must initialize first
producer(ts)
]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
WaitAll
usage example (typescript)
import {WaitAll} from 'task-serializer';
import {producer} from './demo-lib.js';
async function consumer_waitAll(ts: WaitAll){
try{
let r=await ts.waitAll();
console.log(`ts.waitAll() returned`);
console.log(JSON.stringify(r,null,2));
}catch(e){
console.log(`ts.waitAll() caught ${e.message}`);
}
}
async function consumer_waitAllSettled(ts: WaitAll){
let r=await ts.waitAllSettled();
console.log(`ts.waitAllSettled() returned`);
console.log(JSON.stringify(r,null,2));
console.log('consumer finished');
}
async function main(){
let waitAll=new WaitAll({concurrentTaskLimit:2});
await Promise.all([
consumer_waitAll(waitAll),
producer(waitAll),
]);
waitAll=new WaitAll({concurrentTaskLimit:2});
await Promise.all([
consumer_waitAllSettled(waitAll),
producer(waitAll),
]);
}
main()
.then(()=>{console.log('success');})
.catch((e)=>{console.log('failure '+e.message);});
History
- 2.1.0
- typescript interface provided (source also typescript)
- fixed incorrect parameters in example code