miiihi

[19-08-01 14:43:42.140] (Info) ab.buildDeploy.ui.pendingRequests - No value provided
[19-08-01 15:44:57.502] (Info) ab.buildDeploy.ui.buildConfigChanged - {"buildConfig":"Debug","buildType":"Cloud","isHmr":true,"platform":"iOS","useSharedCloud":false,"webpack":{"env":{"aot":{"debug":false,"release":true},"snapshot":true,"sourceMap":true,"uglify":true},"isWebpack":true}}
[19-08-01 15:44:57.508] (Info) ab.buildDeploy.ui.pendingRequests - 1
[19-08-01 15:44:57.516] (Info) ab.buildDeploy.shell.requestCertificatesSetup - {"buildRequestsList":[{"buildConfig":"Debug","buildType":"Cloud","codeSigning":{"certificateFromStore":{"friendlyName":"","serialNumber":"5C867D13E6E1A10D","subject":"C=DE, O=Blaz Miheljak, OU=565463XF44, CN=iPhone Developer: Blaz Miheljak (4F7PBCM8R8), OID.0.9.2342.19200300.100.1.1=2H734KTKH3"},"isPasswordRequired":false,"provision":"C:\\Work\\Catenate\\cert\\Hamster_1.mobileprovision"},"isClean":true,"platform":"iOS","useSharedCloud":false,"webpack":{"env":{"aot":false,"snapshot":false,"sourceMap

miiihi

Gpio interrupt callbacks in Node.js

When using the C++ Gpio method isr or the C function mraa_gpio_isr it's important to know that the passed in function will be called in the context of a low level interrupt.

As such it should be coded very carefully, and typically do as little as possible, in order not to interfere with the environment that has been interrupted.

When using the isr method in Javascript do we have to worry about this kind of thing?

The answer is no, as the logic for the Javascript wrappers ensures that the callback function passed to isr is invoked from the normal Node.js event loop.