By default, KUE uses the first db on Redis. I explicitly changed that by using the db : number option while creating a queue.

KUE-UI is not showing any jobs now.

Is it possible that this DB change caused KUE-UI to "not find" the jobs? I tried adding a db : number to the KUE-UI setup, but that doesn't seem to help.

Saying something about 'jade not known'

Running npm install throws a bunch of errors.
Tried after clearing cache and with root privileges too but still no help

Hey Guys

I was redirected here from the parse-server community. It sounds like a lot of people are using Kue + Kue-UI to replace parse.com scheduled jobs / cloud jobs.

With the Kue + Kue-UI setup, can you create new schedules for jobs through Kue-UI's web ui? Or is Kue-UI just for viewing the state of the Kue based jobs through a web ui? Looking at the screenshots on Kue-UI's github, it's not immediately obvious.

Thanks.

Hello,

Awesome project first of all!

I was wondering if it's possible to customize the kue prefix ?

What is the state of the project in general ?

Thanks!

Is there an option to sort the pages with the most recent jobs first?

Display a notification if a job is deleted or updated

Could be picked up from environment variables

Kue-ui doesn't update its job list (e.g., "complete") after polling. In the sidebar the count updates, but the list doesn't refresh without changing the navigation or updating the page.

Assumption - I know the job id.

If I want to restart my job, I need to scroll down find the required job and then restart it. Sometimes it becomes very difficult. Currently I use the backend api to restart the job. Is there any way to search by job id?

Hi,

I think I've got things setup right, I've been using Kue for a while with the old UI, and I followed your instructions for mounting this UI into my express app.

Here's what I see:

Blank page. Has HTML, nothing in JS console, no assets failed to load. Thoughts?

The left column is fixed width.

If the left column contains tasks that have long names, the count bubbles are pushed down.
If you have many long names, the count bubbles no longer align with the relevant task.

I'll probably PR it, but my proprosed solution is to leave it scroll left/right like it does now, but move the counts to the left instead of the right...

Does kue-ui show the job log for a job? I didn't find it on the UI

TypeError: Cannot read property 'zcard' of null
at Queue.card (/Users/dev/Documents/integrity-automation/node_modules/kue/lib/kue.js:502:14)
at Queue.inactiveCount (/Users/dev/Documents/integrity-automation/node_modules/kue/lib/kue.js:605:17)
at _ (/Users/dev/Documents/integrity-automation/node_modules/kue/lib/http/routes/json.js:305:19)
at exports.stats (/Users/dev/Documents/integrity-automation/node_modules/kue/lib/http/routes/json.js:41:3)
at Layer.handle as handle_request
at next (/Users/dev/Documents/integrity-automation/node_modules/express/lib/router/route.js:131:13)
at /Users/dev/Documents/integrity-automation/node_modules/kue/lib/http/middleware/provides.js:11:36
at Layer.handle as handle_request
at next (/Users/dev/Documents/integrity-automation/node_modules/express/lib/router/route.js:131:13)
at Route.dispatch (/Users/dev/Documents/integrity-automation/node_modules/express/lib/router/route.js:112:3)
at Layer.handle as handle_request
at /Users/dev/Documents/integrity-automation/node_modules/express/lib/router/index.js:277:22
at Function.process_params (/Users/dev/Documents/integrity-automation/node_modules/express/lib/router/index.js:330:12)
at next (/Users/dev/Documents/integrity-automation/node_modules/express/lib/router/index.js:271:10)
at SendStream.error (/Users/dev/Documents/integrity-automation/node_modules/serve-static/index.js:120:7)
at emitOne (events.js:77:13)
at SendStream.emit (events.js:169:7)
at SendStream.error (/Users/dev/Documents/integrity-automation/node_modules/send/index.js:245:17)
at SendStream.onStatError (/Users/dev/Documents/integrity-automation/node_modules/send/index.js:356:12)
at next (/Users/dev/Documents/integrity-automation/node_modules/send/index.js:630:16)
at onstat (/Users/dev/Documents/integrity-automation/node_modules/send/index.js:619:14)
at FSReqWrap.oncomplete (fs.js:82:15)

This error appears, when i shutdown que and create a new Kue again,with in the application.
The error appears on /api/stats call from browser on an interval.

Right order:
Queued, Active, Complete, Failed, Delayed

I am using hapi to create my application. This is created on express, how can I integrate this on my hapi application? I read about proxy hapi routing for this, but not sure about that. Any guidance towards a direction would be highly appreciated.

On the "standard" Kue dashboard it exposes a restful API .. Does this package also expose a restful API and if so -- where can it be found and how to use it? I think I see it doing restful type calls to some restful looking api but everything I try returns a "404" type thing and there doesn't appear to be much documentation on this package .. ??

I made some changes in templates/components/jobs-table.hbs but my changes didn't reflect.

Error while processing route: jobs.show this._initProperties is not a function TypeError: this._initProperties is not a function

When I try to connect to a remote redis server I don't get any jobs listed. I can't even get it to work locally with different databases (I have multiple queues that I want to monitor)

displaying only job.data, job.result in the right details panel

Is there a simple way to make this UI update on an interval like the built-in Kue front-end does?

In the job properties json that is opened when a job is selected, in the progress_data property, only the last progress data appears, while all the other logs/progress data that were sent during the job are missing.

It looks like there is no request for logs of this job ID.
I can see them in the original UI when I select the same job.

kue-ui-client v1.0.2

Tried a very basic setup, but can't get it working
My Setup

    var q = kue.createQueue({
        prefix: 'q',
        redis: {
            port: options.port,
            host: options.host,
            auth: options.password
        }
    });

    s.expose('queue', q);
    s.expose('kue', kue);

    // Admin UI
    //kue.app.mountpath = '/admin/kue';
    // Otherwise u cant run tests while having a server running;
    var port = Math.floor(Math.random() * 1000) + 16000;
    console.log('local port!'+port);
    var app = express();


    ui.setup({
        apiURL: '/api', // IMPORTANT: specify the api url
        baseURL: '/kue', // IMPORTANT: specify the base url
        updateInterval: 5000 // Optional: Fetches new data every 5000 ms
    });

    // Mount kue JSON api
    app.use('/api', kue.app);
    // Mount UI
    app.use('/kue', ui.app);

    app.listen(port);

The error

TypeError: Cannot read property '0' of undefined
    at new View (/Users/marc/Sites/hapigamb/node_modules/express/lib/view.js:41:65)
    at Function.app.render (/Users/marc/Sites/hapigamb/node_modules/express/lib/application.js:485:12)
    at ServerResponse.res.render (/Users/marc/Sites/hapigamb/node_modules/express/lib/response.js:755:7)
    at clientRoute (/Users/marc/Sites/hapigamb/node_modules/kue-ui/lib/kue-ui.js:14:16)
    at callbacks (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/router/index.js:164:37)
    at param (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/router/index.js:138:11)
    at pass (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/router/index.js:145:5)
    at Router._dispatch (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/router/index.js:173:5)
    at Object.router (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/router/index.js:33:10)
    at next (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/node_modules/connect/lib/proto.js:174:15)
    at Object.expressInit [as handle] (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/lib/middleware.js:30:5)
    at next (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/node_modules/connect/lib/proto.js:174:15)
    at Object.query [as handle] (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/node_modules/connect/lib/middleware/query.js:43:5)
    at next (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/node_modules/connect/lib/proto.js:174:15)
    at Function.app.handle (/Users/marc/Sites/hapigamb/node_modules/kue-ui/node_modules/express/node_modules/connect/lib/proto.js:182:3)
    at Object.fn [as handle] (/Users/marc/Sites/hapigamb/node_modules/express/lib/application.js:117:11)

Hi,

I've tried using it behind a proxy with url rewrite rules and it didn't work.

Other than that, looks great.

Is there any reason why current version (1.1.3) is not published to npm?

I refine this into

• removeByState
• removeByState&Type

which is very helpful in production environments.

User can have a empty link under their filtered/sub-menu of state/job_type in current kue-ui which removes all jobs of the current filter/sub-menu.

Goto job: an input to write the job id, to be showed in the UI

Hi Guys

Ive been running nsp on my projects and some vulnerabilities were reported for kue-ui

┌───────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│               │ Regular Expression Denial of Service                                                                                               │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Name          │ uglify-js                                                                                                                          │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Installed     │ 2.2.5                                                                                                                              │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Vulnerable    │ <2.6.0                                                                                                                             │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Patched       │ >=2.6.0                                                                                                                            │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Path          │ [email protected] > [email protected] > [email protected] > [email protected] > [email protected]                                                   │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/48                                                                                              │
└───────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

┌───────────────┬────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐
│               │ Incorrect Handling of Non-Boolean Comparisons During Minification                                                                  │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Name          │ uglify-js                                                                                                                          │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Installed     │ 2.2.5                                                                                                                              │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Vulnerable    │ <= 2.4.23                                                                                                                          │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Patched       │ >= 2.4.24                                                                                                                          │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ Path          │ [email protected] > [email protected] > [email protected] > [email protected] > [email protected]                                                   │
├───────────────┼────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ More Info     │ https://nodesecurity.io/advisories/39                                                                                              │
└───────────────┴────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┘

hello and great job

is there any way in which i could use kue ui when the api endpoint is secured with basic authentication ?

cheers

Requeue failed jobs button. To put on index page.

npm ERR! Command failed: /usr/bin/git checkout feature/fixCSSClean
npm ERR! error: pathspec 'feature/fixCSSClean' did not match any file(s) known to git.

I was able to start kue-ui and spawn a few consumers to process jobs. For verification purposes, I made the server create a new job every few seconds. I could see those job statuses on kue-ui.

My question is: is it possible to manually trigger a job from the UI? If not what's the idiomatic way to trigger a job today?

Thanks!