manufacturing

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

Hi,

For safety use, it's better to have null check for all variables which are used in this function.

if (!_sessionPriv.$clientAlarmList) {
    return;
}

↓

if (!_sessionPriv.$clientAlarmList
     || !_sessionPriv.$monitoredItemForAlarmList
     || !_sessionPriv.$subscriptionforAlarmList ) {
    return;
}

https://github.com/node-opcua/node-opcua/blob/master/pack

Is this a bug or feature request?

FR

What is the current behavior?

not in the tree

What is the expected or desired behavior?

should be under the section "System"

WHAT: Add a new Task type for a shutdown/reboot task.

WHY: An automated TaskList might want to reboot the DUT in the middle of the task flow. Currently, you would need to finish a TaskList, reboot via the API, then resume the TaskList.

HOW: Add a new Task type, which is used for Shutdown or Reboot. When executed as part of a TaskList, the reboot operation is performed and then th