
Security News
Attackers Are Hunting High-Impact Node.js Maintainers in a Coordinated Social Engineering Campaign
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.
Controller of consecutive or concurrent execution of a sequence of asynchronous operations
var AsyncCtrl = require("async-ctrl");
var initialValue = 1;
var scopeObject = {};
AsyncCtrl([
function(success, failure, value, scope) {
setTimeout(function() {
success(value * 2);
}, 1500);
},
[function(success, failure, value, scope) {
setTimeout(function() {
if ( ++scope.successes$ === 2 )
success(value * 3);
}, 2500);
}, function(success, failure, value, scope) {
setTimeout(function() {
if ( ++scope.successes$ === 2 )
success(value * 2);
}, 1500);
}, function(success, failure, value, scope) {
setTimeout(function() {
failure(-value);
}, 3500);
}],
])(initialValue, scopeObject)
.onSuccess(function(value) {
console.log(value); //6
})
.onFailure(function(error) {
console.error(error);
});
The first step is defining the task list. The entry point function (AsyncCtrl) accepts this list and return controller's constructor for this list and its invocation starts the execution. That constructor accepts two optional arguments: initial value for the first task and object meant to imitate the inner scope of the tasks. The constructor returns controller's instance with onSuccess(handler) and onFailure(handler) methods for assigning the execution outcome handlers. The fact of the handlers' invocations is independent of the time they were assigned. It is possible to terminate the further execution by calling the failure(error) method of the instance in which case the failure handlers will be invoked. Ultimately only one group of handlers will be triggered.
The list of tasks is an array containing consecutively executed tasks. Each of these tasks is a function or an array of functions being invoked simultaneously. Successfulness is reported via the first argument of the function and an error via the second one. For each task only the first such report takes effect. Once a successful result is reported the execution process proceeds to the next task or is terminated in case of an error. Each function receives the successful result of the previous task via the third argument and the scope object via the fourth argument. Before the execution of the next task begins the attribute values$ of the scope object is assigned to an empty array and the attributes successes$ and failures$ are assigned to a value 0 which enables communications between concurrently executed functions. The last task's successful result or an error report will be passed to the appropriate outcome handlers.
FAQs
Controller of consecutive or concurrent execution of a sequence of asynchronous operations
We found that async-ctrl demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Security News
Multiple high-impact npm maintainers confirm they have been targeted in the same social engineering campaign that compromised Axios.

Security News
Axios compromise traced to social engineering, showing how attacks on maintainers can bypass controls and expose the broader software supply chain.

Security News
Node.js has paused its bug bounty program after funding ended, removing payouts for vulnerability reports but keeping its security process unchanged.