
Research
Malicious npm Packages Impersonate Flashbots SDKs, Targeting Ethereum Wallet Credentials
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
tbs-cron-queue
Advanced tools
Package for handling cron job queue issue. Will queueing every cron job added with redis distribution between pods. ___Note: This package will running on 5s interval on background to check and pick the queue. Also every cron will be run with inte
Package for handling cron job queue issue. Will queueing every cron job added with redis distribution between pods.
Note: This package will running on 5s interval on background to check and pick the queue. Also every cron will be run with internal api call with axios. So remind that your cron job API with block API mechanism
yarn add tbs-cron-queue tbs-site-config global-body-validator-tbs
npm install tbs-cron-queue tbs-site-config global-body-validator-tbs
For initializing package you need to write in 2 file
import { TbsCronQueueModule } from 'tbs-cron-queue';
@Module({
imports: [
TbsCronQueueModule.register({
options: {
port: +process.env.REDIS_PORT,
host: process.env.REDIS_HOST
},
prefix: process.env.CRON_JOB_QUEUE_PREFIX,
baseUrl: process.env.CRON_JOB_BASE_URL,
site_config_prefix: process.env.KAFKA_TOPIC_PREFIX,
})
],
controllers: [],
providers: [],
})
export class ExampleModule {}
After initialize this module on your app.module, you can see the controller below on swagger with tags name Queue Worker. Just redirect your cron job url to this controller.
In package controller will have 4 API, with detail:
add-queue
=> will add your cron job to redis queueclean-queue
=> will remove all redis queuesingle-queue
=> will remove single cron job data from redis queuehealth-check
=> will return 200 when there's no queue running on pods and 403 when any queue is running on podsadd-queue
will check in redis queue, is that cron job url and method is registered unleash on processing queue or waiting queue. When that cron is in that state, so cron will be rejected, and vice versa when cron is not in any state then will be inserted to waiting queue.
clean-queue
will remove all of processing queue and waiting queue
single-queue
will remove a single cron from processing queue and waiting queue based on http method and url target combination you gave
health-check
will check is this pods is running any queue or not. When the pods running any queue then response will be 403 and cant receive any traffic, vice versa will return response 200. So we recommend that your liveness probe and rediness probe of your kubernetes is directed here.
FAQs
Package for handling cron job queue issue. Will queueing every cron job added with redis distribution between pods. ___Note: This package will running on 5s interval on background to check and pick the queue. Also every cron will be run with inte
The npm package tbs-cron-queue receives a total of 18 weekly downloads. As such, tbs-cron-queue popularity was classified as not popular.
We found that tbs-cron-queue 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
Four npm packages disguised as cryptographic tools steal developer credentials and send them to attacker-controlled Telegram infrastructure.
Security News
Ruby maintainers from Bundler and rbenv teams are building rv to bring Python uv's speed and unified tooling approach to Ruby development.
Security News
Following last week’s supply chain attack, Nx published findings on the GitHub Actions exploit and moved npm publishing to Trusted Publishers.