hans-lizihan / bull-master Goto Github PK

In the main view, you can see the beautiful state graphs, and below the list of all queues.
It would be great to click on a state on a graph, failed for example, and it would filter the list of all queues to only the ones with at least one failed job.

It should be possible by iterating all of the queues, and search for at least one failed using the getJobs('failed') bull method.

First of all, congrats on the neat project 🚀 I was using bull-board but decided to take a look at yours since it has some nice features :)

One thing I was really looking forward was the ability to add jobs to a given queue (something really simple like a input for the json-payload would suffice).

Are you planning on adding something like that? If it is not something on your roadmap would you be interested in a PR?

res.send will properly set the content type for the response while response.end is not meant to be used for sending data. This becomes an issue when using with helmet express middleware which will force this response to be a string instead of html.

Hi, after install i have this errors:

Bull ver 3.18.0

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: undefined. Note: this is a nested preset so please contact the preset author if you are unable to fix it yourself.

Congrats on a great looking package! I am running into an error when I navigate in to see the detail of a queue. Any assistance would be appreciated. I'm pretty new to the node world and not quite sure where to dig into.

TypeError: Cannot read property 'getJob' of undefined
    at module.exports (/Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/controllers/job.js:7:27)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/index.js:20:19
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:281:22
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:354:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)
TypeError: Cannot read property 'getJob' of undefined
    at module.exports (/Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/controllers/job.js:7:27)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/index.js:20:19
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:281:22
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:354:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)
TypeError: Cannot read property 'getJob' of undefined
    at module.exports (/Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/controllers/job.js:7:27)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/bull-master/server/index.js:20:19
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/layer.js:95:5)
    at /Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:281:22
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:354:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)
    at param (/Users/kwolf/code/granville-listener-clustered/node_modules/express/lib/router/index.js:365:14)

Below is the response of api /api/redis-stats

• Redis version lower then 5.0

{
  "redisVersion": "3.0.6",
  "usedMemory": "66331368",
  "memFragmentationRatio": "1.03",
  "connectedClients": "660",
  "blockedClients": "2"
}

• Redis version upper then 5.0

{
  "redisVersion": "5.0.5",
  "usedMemory": "1406312",
  "memFragmentationRatio": "2.89",
  "connectedClients": "7",
  "blockedClients": "2",
  "totalSystemMemory": "2087837696"
}

the lost property totalSystemMemory will trigger the dashboard crash，

bull 3 require redis version > 2.8.18,

so this amazing UI could compatible with lower versions?

many thanks!

Introduction:

Welcome to the exciting world of crypto airdrops! Here's a curated list of active airdrops that you wouldn't want to miss. Dive in and explore the opportunities:

📌 Follow the Step-by-Step Guide to Claim Your Tokens!

1. Share on Social Media:

   🚀 Claim Your Share: Pyth Network Airdrop 🚀 Unlock the potential of $PYTH tokens in this step-by-step guide. Claim yours now! Share on Twitter

   — Pyth Network (@pythnetwork) November 28, 2023

   • Telegram:
     Join on Crypto Airdrops Telegram Chanel

2. Verify Eligibility:
   After sharing and connecting your walle

Active Airdrops:

1. Layer Zero Airdrop

   • 🌐 Layer Zero Website
   • 📰 Medium Article
   

2. Pyth Network Airdrop

   • 🌐 Pyth Network Website
   • 📰 Medium Article
   

3. Mantle Network Airdrop

   • 🌐 Mantle Network Website
   • 📰 Medium Article
   

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• ⬆️ Update dependency @babel/core to v7.24.4
• ⬆️ Update dependency webpack-bundle-analyzer to v4.10.2
• ⬆️ Update dependency css-loader to v6.11.0
• ⬆️ Update actions/setup-node action to v4
• ⬆️ Update dependency axios to v1
• ⬆️ Update dependency babel-loader to v9
• ⬆️ Update dependency bullmq to v5
• ⬆️ Update dependency clsx to v2
• ⬆️ Update dependency css-loader to v7
• ⬆️ Update dependency date-fns to v3
• ⬆️ Update dependency eslint to v9
• ⬆️ Update dependency eslint-config-prettier to v9
• ⬆️ Update dependency eslint-plugin-prettier to v5
• ⬆️ Update dependency husky to v9
• ⬆️ Update dependency lint-staged to v15
• ⬆️ Update dependency nodemon to v3
• ⬆️ Update dependency prettier to v3
• ⬆️ Update dependency prettier-eslint to v16
• ⬆️ Update dependency style-loader to v4
• ⬆️ Update dependency webpack-cli to v5
• ⬆️ Update dependency webpack-dev-server to v5
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• ⬆️ Replace dependency @material-ui/core with @mui/material 5.0.0
• ⬆️ Replace dependency @material-ui/icons with @mui/icons-material 5.0.0
• ⬆️ Update dependency commitlint-config-gitmoji to v2.3.1
• ⬆️ Update dependency eslint-plugin-react to v7.34.1
• ⬆️ Update dependency recharts to v2.12.5
• ⬆️ Update react-router monorepo to v6.22.3 (react-router, react-router-dom)
• ⬆️ Update actions/checkout action to v4
• ⬆️ Update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/core)
• ⬆️ Update dependency jest to v29
• ⬆️ Update dependency pretty-bytes to v6
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Problem: I get a blank dashboard with just a header and footer at /admin/queues

Relevant Code Snippets:
queues.ts

import Queue from 'bull';
import bullMaster from "bull-master";

const dataQueue = new Queue<IMetadataJobData>('metadata-queue', queueOptions);
const upgradeQueue = new Queue<IUpgradeJobData>('upgrade-queue', queueOptions);

const bullMasterApp = bullMaster({
    queues: [dataQueue, upgradeQueue]
});

export default {
    dataQueue,
    upgradeQueue,
    bullMasterApp
}

index.ts

app.use('/admin/queues', queues.bullMasterApp)

Screenshot:

it would be great if timeout would be customizable and not hardcoded

great work guys! 👏

bull-board allows for setting the queues asynchronously. It would be nice to continue to have some way of doing this as it helps with integration with frameworks like NestJS.

Similar to how its described here: https://medium.com/@gdr2409/bull-queues-in-nestjs-306c51cb0ec2

Using CSP headers which disallow unsafe inline scripts breaks bull master. From a quick look it looks like it is mainly due to how basePath is passed to the client.

The generated HTML ends up with:

<script>
      window.basePath = '.....'
</script>

Which breaks CSP (using helmet can be used to expose this). One alternative would be to provide a way to pass the per-request nonce to bull-master (or pick it up from res.locals if set there). Or just completely avoid this mechanism for passing the basePath to the client.

Providing a way to sort the jobs lists by certain attributes, specifically for us delay time (being able to see which one will run next) would be very nice. Maybe something along the lines of clicking on the column name to sort asc / desc?

Secondly, along these same lines. I deal with some queues that have thousands of jobs. Would it be possible to add a page number selector instead of just incrementing through them?

Thanks for this UI tool, its great!

I needed to have separate UIs for separate workflows that may share some queues underneath. At least now I can have separate Pages for separate workflows. Great work on the crisp UI here.
It would be really cool enhancement, if we could choose based on job name.

As the title say, spacing is too big