job-queue

Greetings,

I just clicked on "remove" when I ment to click on retry. (OPPS) Could the resque team consider a minor feature request and place remove on the far left and retry on the far right? This would reduce the possibility of an "irrevokable" mis-click.

I believe this was handled by the wipe-if-demo script in the demo but I needed to manually run it in production since I removed that script from the Procfile. Not a huge deal but figured I would at least document it here to save someone else some time as it threw me for a little loop when I got the Postgres error.

Got the following error when I tried to register since the worker schema was

Correct me if I'm wrong, but pgcrypto only appears to be installed in order to use gen_random_uuid(). That function is available without the extension in Postgres 13+. Is it feasible to make the installation of pgcrypto conditional on version so it can be avoided if unnecessary?

It would be great if there was the ability to provide a, more easily, human readable format for used_memory. At the moment you can't simply glance at it and ingest the provided information.

Specifically, it would be great if this was more easily human readable:
<img width="420" alt="used_memory" src="https://user-images.githubusercontent.com/2548998/29522978-4d6d7eda-8659-11e7-989b-41874e09

https://github.com/mojolicious/minion/blob/f40261615c43a5a2aa25980e5f1e734320df159f/lib/Mojolicious/Plugin/Minion/resources/templates/layouts/minion.html.ep#L6

Hi,
Do you really use "popper.js".
In my case, after deploying plugin, I could not get this file.
My be it's useless line for plugin?

![pooper_js_not_found](https://user-images.githubusercontent.com/11445575/136359705-5f9f0a98-23d5