Checklist

• I have checked the issues list
  for simi

Currently if machinery is misconfigured for the connection to AMQP it will run indefinitely at a exponential backoff. It will be easier for users to detect failure in a production application if the application is allowed to exit out on failures that are not likely going to be recoverable.

Describe
QueueName should not be stored in the table t_ds_user, which can result in inconsistent data.

Reproduce

1. Update queue's name
2. Query Userlist
3. The queue's old name is returned

Expected
The new value should be returned

Version
-[dev]

**Imp

GM Folks,

Small favor/minor request -

For those of us running containerized processes via docker, kubernetes, etc. can we have the
.run() function added as an example to the readme.

I found myself looking through the code for this and think it may be helpful for those coming through later.

For example, see bottom of code snippet

from redis import Redis
from rq import Queue

This is not currently being tested, and as it is a template method, we don't even check it builds correctly.

Is there any tutorial other than quick tutorial, which is good for start, but where to find answers to slightly difficult questions like

1. how to create columns like year / month of date columns.
2. how to create columns like amount which is computed by a formula.
3. how to create drill-down report.

all these samples are available in code but how to create on your tables, right from scra

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.

Something to the effect of:
Copyright 2020 by the FiberTaskingLib Contributors

Similar for all the file headers.

Then create a Contributors.txt file that lists all the contributors.

Introduce new command that read/tail error/info log

Possible read commands:

• leprechaun error-log
• leprechaun info-log

Possible tail commands:

• leprechaun tail-error-log
• leprechaun tail-info-log

These commands will try to read global error and info logs if they are specified as global. Every service can have it's own error and info log so we should include default commands in age