
Research
/Security News
Critical Vulnerability in NestJS Devtools: Localhost RCE via Sandbox Escape
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
async-await-retry
Advanced tools
Minimalist, efficient and performance focused retry system. Basically it helps developer to retry a function with a specific interval, exponential factor etc.
No dependency.
/!\ This module use async/await syntax, this is why you must have node 7.6+.
Supported and tested : >= 7.6
Version | Supported | Tested |
---|---|---|
20.x | yes | yes |
18.x | yes | yes |
16.x | yes | yes |
14.x | yes | yes |
12.x | no | yes |
10.x | no | yes |
9.x | no | yes |
8.x | no | yes |
>= 7.6 | no | yes |
$ npm install async-await-retry --save
const retry = require('async-await-retry');
const func = async () => {return new Promise((resolve) => resolve('OK'))};
try {
const res = await retry(func)
} catch (err) {
console.log('The function execution failed !')
}
const retry = require('async-await-retry');
const func = () => {...};
try {
const res = await retry(func)
console.log(res) // output : OK
} catch (err) {
console.log('The function execution failed !')
}
const retry = require('async-await-retry');
try {
const res = await retry(async () => {
return new Promise((resolve) => resolve('OK'))
})
console.log(res) // output : OK
} catch (err) {
console.log('The function execution failed !')
}
const retry = require('async-await-retry');
try {
const res = await retry((arg1, cb) => {
....
cb(err, data); // send err as first argument
}, ["arg1"], {isCb: true});
} catch (err) {
console.log('The function execution failed !')
}
## retry(function, [args], [config])
function
: function to retry in case of errorargs
: your function's parameters in case you don't use callback styleconfig
: an object containing all retry process optionsOption | description | Default value |
---|---|---|
retriesMax | Maximum number of retries | 3 |
interval | Delay in ms between two tentatives | 0 |
exponential | Will the interval increase exponentially ? | true |
maxBackoff | Maximum delay before to retry (with exponential) | 30s |
factor | The exponential factor to use | 2 |
jitter | Random jitter in ms to add to the interval | 0 |
isCb | Old callback function style ? | false |
onAttemptFail | User's callback to manage retry system | default fallback |
An example of custom options :
const retry = require('async-await-retry');
try {
const res = await retry(async () => {
return new Promise((resolve) => resolve('OK'))
}, null, {retriesMax: 4, interval: 100, exponential: true, factor: 3, jitter: 100})
console.log(res) // output : OK
} catch (err) {
console.log('The function execution failed !')
}
This method can be used to manage, by yourself, the retry system. It's called when an error occurred and before to retry. This method can have three behaviors:
const retry = require('async-await-retry');
try {
const res = await retry(MyfuncToRetry, null, {
onAttemptFail: (data) => {
// do some stuff here, like logging errors
}
});
} catch (err) {
console.log('The function execution failed !')
}
The data argument is an object that can be described like this:
Property | description |
---|---|
error | The current error object |
currentRetry | The current retry value |
retriesMax | Maximum number of retries |
interval | Delay in ms between two tentatives |
exponential | Will the interval increase exponentially ? |
factor | The exponential factor to use |
jitter | Random jitter in ms to add to the interval |
maxBackoff | Maximum delay before to retry |
$ npm test
Coverage report can be found in coverage/.
FAQs
Simple module to retry a function with async/await syntax !
The npm package async-await-retry receives a total of 2,781 weekly downloads. As such, async-await-retry popularity was classified as popular.
We found that async-await-retry 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.
Research
/Security News
A flawed sandbox in @nestjs/devtools-integration lets attackers run code on your machine via CSRF, leading to full Remote Code Execution (RCE).
Product
Customize license detection with Socket’s new license overlays: gain control, reduce noise, and handle edge cases with precision.
Product
Socket now supports Rust and Cargo, offering package search for all users and experimental SBOM generation for enterprise projects.