There's the easy way, which is just to document job.requeue() on the jobs documentation page:

https://github.com/rq/rq/blob/master/rq/job.py#L527

I could be wrong, but I don't think that (super important) method is actually documented anywhere! I found it by searching the Github issues.

And there's the hard way, which would be to provide this information with a full example of u

I‘v noticed that there is no Etag returned in static files response , any plans to add support for it?
Or, add a config item for it.

In the web UI, While Clicking one of the Worker Name, WebUI does not take to the respective page rather it is unresponsive.

**Worker Name | Status | Active | Processed | Failed | Succeeded | Retried | Load Average
celery@abc.com| online | 0 | 2 | 0 | 2 | 0 | 0.06, 0.1, 0.09
celery@bcd.com| online | 0 | 3 | 0

Some people seem to read https://html.spec.whatwg.org/multipage/forms.html#dom-form-nameditem as implying that a new nodelist should be returned each time when there are multiple matching elements. That's not the intent, I assume, and it might be worth clarifying the spec to make it clear.

All browsers I tested (Firefox, Chrome, Safari) return the same nodelist on multiple accesses.

Hi,

any plan for supporting the upcoming [webpack 5][11]?

I had a quick try and I istantly hit a wall at this point which should be updated to:

import ParserHelpers from 'webpack/lib/javascript/JavascriptParserHelpers';

Thanks 💯 for the awesome lib!

I want to select all items that have been successfully processed by honeydew, I guessed by looking at the source code that I can use where([x], is_nil(x.honeydew_whatever_lock)) to do this, but this couples my code tightly against honeydew implementation details, I'd like a more "official" or "public" way to achieve this.

https://github.com/koudelka/honeydew/blob/b60b639d6b2b3253f1bb20246df48

Is your feature request related to a problem? Please describe.
Currently, we can only see how many tasks have been enqueued in each queue using the CLI.
It'd be better if we can show the latency of each queue in the output so that user can tell when was the oldest task in the queue was enqueued.

Describe the solution you'd like
Show the latency within the stats command output.

Crash java.lang.RuntimeException: java.util.concurrent.ExecutionException: java.lang.RuntimeException: Unable to load script from assets 'threads/pre-load-data-worker.thread.bundle'. Make sure your bundle is packaged correctly or you're running a packager server.

![screen shot 2018-07-28 at 11 29 18](https://user-images.githubusercontent.com/3612098/43357535-8379af28-9259-11e8-9c5a-96

workerNodes.call : Proxy

This exposes the api of a module that the worker nodes are working on. If the module is a function, you can call this directly. If the module exports multiple functions, you can call them as they were properties of this proxy.

Kind: instance property of WorkerNodes

nothing is mentioned about promises, and the example shows usage of promises

On our install, sometimes we see the same job for the same hook being duplicated multiple times with the same nextrun timestamp.

Regardless of my example, instead of using a SQL query to delete a job or multiple jobs, it would be handy if there was a wp-cli command that allowed us to remove said jobs.

If this sounds like a good idea, I recommend wp cavalcade job delete for this new subco

See discussion end of #662

logging explicit instructions to install @loaders.gl/polyfills if polyfills are detected as missing would certainly help anyone else who may find themselves facing similar issues.

Core could e.g. look for TextDecoder on global scope and issue a warning.

loading the following URL in the browser:

http://localhost:8081/index.worker.bundle

results in the packager error printed to the terminal running the packager:

Error: Error validating module options: child "platform" fails because ["platform" must be a string]
at /Users/mmmurf/projects/react-native-workers/example/node_modules/react-native/packager/react-packager/src/lib/declareOpts.

Please document the needed steps to run, test, and develop the plugin. Also any conventions future developers should follow/ things they should know