Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
promise-parallel-throttle
Advanced tools
Run a array of Promises in parallel. Kinda like Promise.all(), but throttled!
npm i promise-parallel-throttle -S
yarn add promise-parallel-throttle
import Throttle from 'promise-parallel-throttle';
//Function which should return a Promise
const doReq = async (firstName, lastName) => {
//Do something async.
return firstName + " " + lastName;
}
const users = [
{firstName: "Irene", lastName: "Pullman"},
{firstName: "Sean", lastName: "Parr"}
];
//Queue with functions to be run
const queue = users.map(user => () => doReq(user.firstName, user.lastName));
//Default Throttle runs with 5 promises parallel.
const formattedNames = await Throttle.all(queue);
console.log(formattedNames); //['Irene Pullman', 'Sean Parr']
Throttle.all(tasks, maxInProgress = DEFAULT_MAX, failFast = true, progressCallback, nextCheck = defaultNextTaskCheck)
Throttle.all is made to behave exactly like Promise.all but instead of all the tasks run parallel it runs a max amount of tasks parallel. All the parameters are optional instead of tasks array which is required. For the defenition of the other parameters see Throttle.raw
Throttle.sync(tasks, failFast = true, progressCallback, nextCheck = defaultNextTaskCheck)
Throttle.sync runs all the tasks synchronously. All the parameters are optional except for the tasks array. For the defenition of the other parameters see Throttle.raw
Throttle.raw
requires only a array of functions to work properly. However there are more parameters.
Throttle.raw(tasks, maxInProgress = DEFAULT_MAX, failFast = false, progressCallback, nextCheck = defaultNextTaskCheck)
Parameter | Type | Default | Definition |
---|---|---|---|
tasks | Array | Required | queue of tasks to be run |
maxInProgress | Integer | 5 | max amount of parallel threads |
failFast | Boolean | false | reject after a single error, or keep running |
progressCallback | Function | Optional | callback with progress reports |
nextCheck | Function | Optional | function which should return a promise, if the promise resolved next task is spawn |
The progressCallback and the Throttle itself will return a object with the following properties:
Property | Type | Start value | Definition |
---|---|---|---|
amountDone | Integer | 0 | amount of tasks which are finished |
amountStarted | Integer | 0 | amount of tasks which started |
amountResolved | Integer | 0 | amount of tasks which successfully resolved |
amountRejected | Integer | 0 | amount of tasks which errored and are aborted |
rejectedIndexes | Array | [] | all the indexes in the tasks array where the promise rejected |
resolvedIndexes | Array | [] | all the indexes in the tasks array where the promise resolved |
taskResults | Array | [] | array containing the result of every task |
All the functions got a parameter which will use the passed function as a check before spawning the next task.
The default nextCheck
look like this;
const defaultNextTaskCheck = (status, tasks) =>
return new Promise((resolve, reject) => {
if (status.amountStarted < tasks.length) {
return resolve(true);
}
resolve(false);
});
This function will get a status object as parameter which adheres to the object in Result / Progress callback and the list of tasks. In the default we simply check if the amount of started exceeds the amount to be done, if not we are free to start a other task.
If a custom implementation decides to reject the error is propagated and should be handled in the user it's code.
This function can be useful to write your own scheduler based on, for example ram usage/cpu usage.
Lets say the tasks you defined use a lot of ram and you don't want to exceed a certain amount.
Then you could write logic inside a nextCheck
function which resolves after there is enough ram available to start the next task.
Check out the example's directory, it's heavily documented so it should be easy to follow.
To run the example, at least Node 7.x.x is required, since it supports native async/await.
Simply run the example with npm:
npm run-script names
Or with Yarn:
yarn names
FAQs
Run promises in parallel, but throttled
The npm package promise-parallel-throttle receives a total of 21,689 weekly downloads. As such, promise-parallel-throttle popularity was classified as popular.
We found that promise-parallel-throttle demonstrated a healthy version release cadence and project activity because the last version was released less than 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
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.