A static archive of Markus Tacker's tweets. Follow me on Mastodon: @[email protected].
That moment when you no longer can put off migrating to AWS IoT SDK v2 for
JavaScript: https://github.com/aws/aws-iot-device-sdk-js-v2
It's much less convenient that v1, so this is going to take a while to migrate
the existing end-to-end tests I use it in.
It's because of these error messages I'm not really excited about this upgrade:
Aaand of course I found a bug already:
https://github.com/aws/aws-iot-device-sdk-js-v2/issues/176
Cramming a C library through Node.js is such a PITA.
I absolutely need to catch connection exceptions during end-to-end tests because
we use JITP and the device will get disconnected on the first connect. During
the test this is expected and needs to be gracefully handled in the test run.