fogine

After further investigation I've found out that this error is triggered [HERE](https://github.com/dthree/vantage/blob/master/bin/vantage.js#L63). The `vantage` variable refers to the `Vorpal` object which does not have the `_pause` property at all.

> However, I don’t seem to be able to use vorpal’s types method as specified here Last released version of `vantage` (to npm) uses old version of `vorpal` v1.0.5 which...

For me that is also a lot desired feature.

Now script parses only function header ( public function set($arg) ), not body of function... In function template, there are available variables: {{indent}} {{scope}} {{static}} {{name}} - parameter variables On...

> Nope, It is not the responsibility of this lib. > You control your queues. > There is not good reason to make it available from the UI (if you...

@revathskumar & @felixmosh I refer to this `job.getState() === 'stuck'`.. According the following documentation and source code, the job can get into `stuck` state even though its not documented much...

The following test case implies that job can get into a `stuck` state when its not found in any other state https://github.com/OptimalBits/bull/blob/b50512e1a823f01393bc4a72d2b028c032f8a678/test/test_job.js#L267

If thats the case, it is quite important to know about such jobs and be able to clean them.. I experienced an issue where I could not create a job...

I'm sure that `job.releaseLock` does not get called anywhere in the related project. In my opinion, if job can get into such state, it would be useful to see those...

Hm, I think it might be related only to the [bulljs](https://github.com/OptimalBits/bull) project, not `bullmq`. As `bulljs` was completely rewritten to `bullmq` it seems that `stuck` jobs does not exist there...