MQTT issue fixed

BUG fixed

• pubsub samples from iot-device-sdk-js-v2 exit with non-zero code
• on_publish callback is not cleaned up

Dependency update for security vulnerability

Async callback fix

BUG FIXED

• Async callbacks invoked with env is gone and leads to a crash
• The eventloop-group created for node never cleaned up.
• Asynced write operation for a Bufferarray based on a C managed buffer will crash, as the C buffer get cleaned up after the callback, before the async operation finishes.

Fix aws-c-cal submodule

v1.5.2

Fix submodule that accidentally went back in time (#181)

Support ArrayBuffer for outgoing MQTT Payloads

v1.5.1

update dependencies for security (#180)

Incoming MQTT payloads are ArrayBuffer again

• Undo API change from v1.4.0. Incoming MQTT payloads are ArrayBuffer again.
• Accept any ArrayBufferView type (ex: Uint8Array) for outgoing MQTT payloads.
• Fix browser MQTT publish() bug that prevented sending anything but strings.
• Fix browser MQTT unsubscribe()
• Fix import of sibling CRT lib

Incoming MQTT payloads are Uint8Array

• API CHANGE: Incoming MQTT payloads are now type Uint8Array. This change affects the on_message event, and the topic-specific callback passed to subscribe().
  • Previously, the payload type definitions claimed they were different in the event vs the callback (Buffer for event and ArrayBuffer for callback), but in fact Buffer was passed to both in the browser implementation, while ArrayBuffer was passed to both in the node implementation. Now it's consistent and correct.
  • Users that were doing new Uint8Array(payload) in their code, like the samples were doing, should be unaffected (though the transformation is no longer necessary).
• API ADDITION: The MQTT on_message event, and the topic-specific callback passed to subscribe(), have added dup, qos, and retain params.
  • This is a backwards compatible change, since users are free to pass a callback that takes less params

Updated libcrypto to get EVP_CipherUpdate overflow fix

v1.3.9

Minor modification to package.json to push a new release

Fix MQTT websocket reconnect crash

Fix crash on websocket reconnect. (#168)

Bug was that `transform_websocket_args` pointer was being destroyed after 1st use, but pointer was re-used for any future reconnects, leading to access violoations. Solution is to create a new `transform_websocket_args` each time a transformation occurs.

Also moved a LOT of logic into the internal MQTT new() call, instead of the internal connect() call. I moved things that only needed to be set once (ex: websocket transform fn). I also added a bunch of cleanup to the finalize() function. It didn't used to do anything, which seemed wrong...

Update axios dependency

• Bump axios from 0.19.2 to 0.21.1

Windows try-lock fix

Try lock fix (#163)

* Fix try-lock on Windows
* Dependency updates