diff options
| author | Michal Kuratczyk <mkuratczyk@vmware.com> | 2021-04-29 09:07:44 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-29 09:07:44 +0200 |
| commit | 95ef9fb69398e5c928836d8e652db6b53f78d817 (patch) | |
| tree | ca8d709c498d7769d54b107ad2c81edaa3a2d173 | |
| parent | 80d35fdaf314a4931bb68c2bb65db5ea64a5c2e0 (diff) | |
| download | rabbitmq-server-git-autoack-clarification.tar.gz | |
More accurate ack mode description in the UIautoack-clarification
I ran into this when working on metrics. This option sets `no_ack = true` which means an automatic ack. However, the old description, `Ack message requeue false`, suggests to me that there is a manual ack. I spent a lot of time trying to find a bug in the metrics code that counted this as an auto-acked message, when in fact it was an auto-acked message. :)
| -rw-r--r-- | deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs b/deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs index e3ac572fde..d6c4c28360 100644 --- a/deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs +++ b/deps/rabbitmq_management/priv/www/js/tmpl/queue.ejs @@ -310,7 +310,7 @@ <td> <select name="ackmode"> <option value="ack_requeue_true" selected>Nack message requeue true</option> - <option value="ack_requeue_false">Ack message requeue false</option> + <option value="ack_requeue_false">Auto ack message requeue false</option> <option value="reject_requeue_true">Reject requeue true</option> <option value="reject_requeue_false">Reject requeue false</option> </select> |