messaging

Currently, some methods in PlainPermissionManager do not have the corresponding test case in PlainPermissionManagerTest. such as
createAclAccessConfigMap, updateAclConfigFileVersion, updateGlobalWhiteAddrsConfig, deleteAccessConfig.
Does anyone want to fulfill it?

This meta issue contains various ideas that may never be implemented, it's a good place to put things that could create useless noise in the issues section

Misc

• add a way to configure the CLI and apps to have two loggers, a full one in JSON in a file + a filtered one formatted for console on stdout
• add i18n support on CLI help messages
• add i18n support on error message

It currently says: "qTox is a powerful Tox client that follows the Tox design guidelines."

Problems:

1. No need to say that this is qTox, because this is obvious from the application name.
2. It isn't translated. Other apps have many sections like this:

Comment[fr]=Xxx
Comment[it]=Xxx

I recommend: "Qt 5 based Tox instant messenger for secure communication"
No need for the peri

The current set of Heron documentation does not mention any of the message handling details such as "anchoring" and "ack/fail" logic. There are some brief mentions to ack and fail in Interface discussion, but Heron should have documentation similar to the logic described here: https://storm.apache.org/releases/1.2.3/Guaranteeing-message-processing.html

Environment

• VerneMQ Version: 1.11.0
• OS:
  Distributor ID: Ubuntu
  Description: Ubuntu 18.04.5 LTS
  Release: 18.04
  Codename: bionic
• Erlang/OTP version (if building from source): 19
• VerneMQ configuration (vernemq.conf) or the changes from the default
• Cluster size/standalone:

Expected behaviour

Connection to Redis server running on unixsocket, configured within Lua scr